Repository navigation
Feature request: incorporate local FS support into the main artefact #657
Description
In contrast to the CAP node.js version of the plugin one needs to include a different dependency into their project when local filesystem mode for local development is needed. This is a bit counterintuitive to what we have in CAP node.js and also to what we haven in other CAP Java features. The plugin or feature should detect itself that it runs locally and then use the local filesystem. This can be achieved by reacting to Spring profiles.
Activity
Schmarvinius commentedon Dec 11, 2025
@rjayasinghe Ultimately I think that is a good idea, but by using spring profiles, we would need to add spring as a dependency. I thought cap-java is framework-agnostic, so you are not bound to use spring/spring-boot, which is obviously the main framework being used, but there is probably 1% that doesn't use spring, and we would introduce this dependency upon them. We would like to enable attachments for all cap java apps.
Did cap-java change that approach of agnostic design?
moustafa186 commentedon Jan 8, 2026
the dependency mentioned in fs storage target page doesn't exist, https://github.com/cap-java/cds-feature-attachments/tree/main/storage-targets/cds-feature-attachments-fs
and I was able only to find this one on maven central: https://central.sonatype.com/artifact/com.sap.cds/cds-feature-attachments-root/1.2.4/overview
which one is the correct one to use?
Schmarvinius commentedon Feb 27, 2026
I'm sorry for the late response. We published the fs-module in the latest release as well. Be aware that this should only be used for local testing purposes. @moustafa186
https://central.sonatype.com/artifact/com.sap.cds/cds-feature-attachments-fs