|Dependencies of same plugin with different versions [message #1385092]
||Wed, 04 June 2014 09:55
|| Jonathan Dumont
Registered: March 2011
We try to migrate an Eclipse RCP product, based on features, to Eclipse 4 using the compatibility layer.
This changed our plugins dependencies as some of the tools integrated to our product have evolved. The problem is that we now depends of some plugins with several versions. For example, we need org.apache.batik.css but for both versions [1.6.0, 1.7.0) and [1.7.0, 1.8.0).
We have built a target platform and a repository with the both versions. The first one is used for our development Eclipse instance, the second one is referenced by our Tycho build.
With Tycho, we managed to build our product with the both versions of the plugin. Our .product definition is based on features and has not been changed.
In the Eclipse instance used for development, we managed to build a launch configuration based on plugins, and manually include the both versions, and it works. But we didn't managed to build a launch configuration based on features, which includes and starts the both versions of the needed plugin...
How can I define in my features that they depends of a plugin, with several versions ? It seems that if I specify the both dependencies, only one is respected.
Thanks for your advices.
Powered by FUDForum
. Page generated in 0.03901 seconds