Hi,
I would like to build bundles without including the sources but still deploy separate source bundles to an in-house maven repository. My intention is that the sources will then be available for debugging purposes via the 'Add Sources' feature.
I'm using the MavenBndRepository with the following instructions in my workspace bnd file,
-sources: false
-maven-release: \
sources;path=${project}/src/
This doesn't work exactly as expected. The source code is deployed but the suffix seems to be derived from the project name (e.g. 'sources.api' or 'sources.provider') instead of the expected 'sources.jar'. This seems to confuse the 'Add Sources' feature as it remains greyed-out in the repository view for downstream workspaces.
I can work around this as follows to get the desired result,
-sources: false
-maven-release: \
sources;path=${project}/src/com/..
Questions:
- Is this simply a bug or is there a different/better way of achieving the same thing?
- If I were to move forward with this work around for the moment, to what extent could I rely my use case being supported in future?
I'm using Bndtools 3.5.0.REL-20170929-190052-ga0d7a6b.
Thanks!
John
--
You received this message because you are subscribed to the Google Groups "bndtools-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bndtools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tested with biz.aQute.bnd.gradle-4.0.0.201801291207-SNAPSHOT.jar. Works as expected.
Many thanks,
John