PDE can have extra dependencies in the bundle.properties. I’m not sure if this can solve your specific issue, however. See an example
That being said, we also have optional dependencies to a lot of unwanted bundles, just because they are needed at IDE time for code generation,
due to using EMF code generation, xtext generation and others. We have target platform filters in the target-platform-configuration POM section, which ensure these bundles never become part of the product. Maybe that at least gives you an additional safety
net when building your product:
Von: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
Im Auftrag von Sebastien Arod
Gesendet: Montag, 21. Dezember 2015 08:37
An: Tycho user list
Betreff: [tycho-user] Annotation Processor & other Compile only dependencies
I'm trying to enable
google autovalue on a tycho project.
Currently to make it work I have to:
* Osgify the bundle.
* Add the bundle to the target platform
* Add the autovalue bundle as an "optional" dependency on google autovalue
I have to osgify the bundle because the autovalue team doesn't want to include the OSGI metadata because they consider the osgi metadata as runtime metadata and their library is used at compile time only without any presence at runtime.
The setup I have seems to work. However it seems a bit of a hack to use an optional dependency to describe a compile only dependency.
Is there a cleaner way to deal with compile time dependencies in PDE/tycho world?