Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migr

[Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>]

Hi,

> This problem looks like it's not caused by the migration of your
> sub-features and you'll probably get a different result with e.g. an Eclipse
> Classic with Code Recommenders 1.x installed and attempting the update there.
> 
> Rather, it's not possible to replace the old o.e.r.rcp.feature with
> something else, because it is required by the EPP DSL Feature upstream. The
> reported conflict is then probably a result of P2 trying to keep the old
> feature and installing the new one, too.

Yes, EPP DSL requires the old feature: "o.e.r.feature.rcp". Apparently,
telling it through p2.inf that that got renamed to "o.e.r.rcp.feature"
is not enough.

> In the end, your migration feature idea is probably still best, if you want
> users to be able to update - assuming that the offending EPP feature doesn't
> get updated for Kepler SR2.

Well, as David explained we can't update to 2.x ourselves in Kepler SR2. :-(

If you meant, however, that the maintainers of the EPP DSL feature could
have done something different, I am not sure what that would be. They
just require (not include) "o.e.r.feature.rcp" without a version
constraint. It looks like this requirement doesn't get rewritten to
"o.e.r.rcp.feature", though.

But the migration feature works and with a require [1] rather than an
include we may even be able to phase out the feature in due time.

Thank you for you help.

Andreas

[1]
<https://git.eclipse.org/r/#/c/20487/2/features/org.eclipse.recommenders.feature.rcp/feature.xml>

-- 
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940