|
Re: force update of existing feature when installing new feature [message #1679576 is a reply to message #1669520] |
Mon, 16 March 2015 17:21 |
Eclipse User |
|
|
|
There's a few issues here. It sounds like
- plugin_A is a singleton (only one version can be installed at a time);
- you've installed feature_A and feature_B as top-level requirements (aka root IUs);
- you've created your features with plugin_A specified as a normal plugin.
Features specify an *exact* version of a bundle. When you update feature_A, p2 ensures that all existing constraints are still met, but since feature_B requires plugin_A 1.0.0, then the new version of feature_A has a conflicting requirement with feature_B, the update fails.
Solutions are:
- Relax the version constraints on feature_B on plugin_A (see the 'depends' tab)
- Update feature_B to 2.0 that includes plugin_A 2.0
- Make plugin_A be non-singleton, such that multiple version can be installed simultaneously (but this can introduce problems with two bundles using different versions of plugin_A)
The p2 FAQ has more detail.
Brian.
|
|
|
Powered by
FUDForum. Page generated in 0.01673 seconds