| Plugin Version Compatibility [message #326521] |
Fri, 21 March 2008 17:12 |
Eclipse User |
|
|
|
Originally posted by: douglas.wieland.osv.fedex.com
Hello,
Is there a way that plugins 1 and 2 requiring different conflicting
versions of a common plugin can work in the same RCP plugin environment?
The project I am working on has a requirement that when the RCP project is
released it will identify the required plugins and versions not allowing
dependent plugin versions to change at the major revision level. There
are common plugins being used with other projects. The common plugins
should be able to be upgraded without impacting other projects.
My tests have used the plugin manifest to specify the required plugins and
have a form of:
Require-Bundle: com.common.plugin;bundle-version="[1.0.0,2.0.0)
I have even experimented with the ;visibility:=reexport option and it has
not change the base incompatibility problem.
The problem arises when there are 2 plugins requiring the common plugin,
but they conflict in the version allowed. If plugin 2 is installed and
has version 2.0.0 for com.common.plugin and also has a Require-Bundle
statement that does not allow for version 1 of the common plugin the
plugin requiring version 1 of the common plugin stops working even though
there is a version 1 of the common plugin available in addition to version
2.
Is there a way that both plugins 1 and 2 requiring different versions of
common plugin can work in the same RCP plugin environment?
Thanks
Doug
|
|
|
Powered by
FUDForum. Page generated in 0.02837 seconds
] 
Search
Help
Register
Login
Home
