This works in my toy example where the plugin is installed for the first time, however in my application I get dependency problems from the other plugins in feature.xml that import this plugin.
Is there some way to keep the bundle in feature.xml and force it to use the latest version of Feature, with the p2.inf with metaRequirements.range=1.0.0.$qualifier$ placed in another feature (CallingFeature) that has no other dependencies on Plugin? P2, however, doesn't just override the previous Feature, instead giving me the error below when, for example, going from v732 to v956. This dependency conflict seems trivial to me since I just want the latest version. What is going on?
Your original request has been modified.
"Feature" is already installed, so an update will be performed instead.
"CallingFeature" is already installed, so an update will be performed instead.
The actions required to successfully install the requested software are incompatible with the software to install.
Cannot complete the install because of a conflicting dependency.
Software being installed: org.eclipse.equinox.p2.engine.actions.root.DefaultProfile 1.0.0.1708587975572
Software currently installed: Feature 1.0.0.202402220732 (com.project.plugin.feature.feature.group 1.0.0.202402220732)
Only one of the following can be installed at once:
Plugin 1.0.0.202402220956 (com.project.plugin 1.0.0.202402220956)
Plugin 1.0.0.202402220732 (com.project.plugin 1.0.0.202402220732)
Cannot satisfy dependency:
From: Feature 1.0.0.202402220732 (com.project.plugin.feature.feature.group 1.0.0.202402220732)
To: org.eclipse.equinox.p2.iu; com.project.plugin [1.0.0.202402220732,1.0.0.202402220732]
Cannot satisfy dependency:
From: org.eclipse.equinox.p2.engine.actions.root.DefaultProfile 1.0.0.1708587975572
To: org.eclipse.equinox.p2.iu; com.project.plugin 1.0.0.202402220956
]]>