JSLMPR abf1259397 The ClipProcessor symbol issue is fixed now. ... The root cause was that ClipProcessor had been updated to call objectStoragePort.uploadGeneratedClip(...), but src/main/java/org/example/videoclips/storage/ObjectStoragePort.java did not yet declare that method. I added it to the port and confirmed both adapters implement it: - src/main/java/org/example/videoclips/storage/InMemoryObjectStorageAdapter.java - src/main/java/org/example/videoclips/storage/S3ObjectStorageAdapter.java I also verified the generated-clip contract is aligned across: - src/main/java/org/example/videoclips/processing/GeneratedClip.java - src/main/java/org/example/videoclips/processing/VideoClipperPort.java - src/main/java/org/example/videoclips/processing/StubVideoClipperAdapter.java - src/main/java/org/example/videoclips/processing/FfmpegVideoClipperAdapter.java		2026-07-09 00:19:44 +02:00
..
upl_5ad28940dd95	The ClipProcessor symbol issue is fixed now.	2026-07-09 00:19:44 +02:00
upl_367df9ed2414	The storage port now has a real staging operation:	2026-07-09 00:02:05 +02:00
upl_b96dfa0dedbe	Generated clips now have a persisted object location instead of being metadata-only. I added objectKey to src/main/java/org/example/videoclips/domain/Clip.java, mapped it through JPA in src/main/	2026-07-09 00:16:49 +02:00
upl_d0599ff63186	The ClipProcessor symbol issue is fixed now.	2026-07-09 00:19:44 +02:00