Hello p2 gods,
we're about to release
m2e-wtp from Eclipse.org and, in order to minimize user disruption, would like to make the m2e-wtp feature upgradeable over it's ancestor (
m2eclipse-wtp, from github). So basically our requirements are :
1 - m2e-wtp and m2eclipse-wtp can not be installed together
2 - m2e-wtp should be able to upgrade itself AND
m2eclipse-wtp
Now #2 is where we're hitting a wall. I tried Pascal's suggestion to modify the content.xml from the update site's content.jar by doing the following :
1 - add "
providedCapabilities.exists(pc | pc.namespace == 'org.eclipse.equinox.p2.iu' && (pc.name == 'org.maven.ide.wtp.feature.feature.group' || pc.name == 'org.eclipse.m2e.wtp.feature.feature.group' && pc.version < '${version}'))" to feature.update.match
2 - remove the id and range attributes from feature.update
The whole script works as expected (the content.xml is properly tweaked, after the site is generated by tycho) but the problem is, the hack doesn't work : m2e-wtp 0.16.0 is still not upgradeable over m2eclipse-wtp 0.15.2 and complains about the conflict declared in p2.inf
Any help/ideas are more than welcome.
Regards,
Fred Bricon
--
"Have you tried turning it off and on again" - The IT Crowd