It appears to me that this Equinox server feature:
org.eclipse.equinox.server.p2.feature.group
is defined to depend upon an older version of org.eclipse.ecf.identity
bundle than the o.e.ecf.core.feature (which is in Luna).
I think that the fix would be to have the more recent version of the
equinox.server.p2.feature be created to use the most recent version of
ecf.identity (i.e. the one in Eclipse Luna RC1). Another option would be
for the equinox.server.p2.feature to refer to the
o.e.e.core.feature...as Eclipse Luna now does...rather than directly to
the ecf.identity bundle.
I would suggest opening a bug against the Equinox server.p2.feature, and
please add me directly to the bug.
WRT aggregator checks...frankly I'm not sure where such an enhancement
would be appropriate...David or others can probably advise.
WRT feature to remove...I would first try removing
org.eclipse.equinox.server.p2.feature.group.
Thanks,
Scott
On 5/14/2014 12:59 AM, Mickael Istria wrote:
Hi all,
If I try to install most pieces of Luna M7 together in a p2
installation, or in a target-definition with "planner" mode (that will
behave similarly to p2 director), then I see an incompatibility
between 2 features:
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed:
org.eclipse.ecf.core.feature.feature.group 1.1.0.v20140505-2203
[ERROR] Software being installed:
org.eclipse.equinox.server.p2.feature.group 1.2.100.v20140428-1446
[ERROR] Only one of the following can be installed at once:
[org.eclipse.ecf.identity 3.4.0.v20140505-2203,
org.eclipse.ecf.identity 3.4.0.v20140428-1446]
[ERROR] Cannot satisfy dependency:
org.eclipse.ecf.core.feature.feature.group 1.1.0.v20140505-2203
depends on: org.eclipse.ecf.identity [3.4.0.v20140505-2203]
[ERROR] Cannot satisfy dependency:
org.eclipse.equinox.server.p2.feature.group 1.2.100.v20140428-1446
depends on: org.eclipse.ecf.identity [3.4.0.v20140428-1446]
The Eclipse M7 build (
http://download.eclipse.org/eclipse/updates/4.4milestones/S-4.4M7-201405010200/
) doesn't contain the
org.eclipse.ecf.core.feature.feature.group/1.1.0.v20140505-2203 and
seems to contain an older one which would be compatbile with
org.eclipse.equinox.server.p2.feature.group/1.2.100.v20140428-1446
So I'm wondering:
* I'd like to open a bug to report that, but I'm not sure who's to
blame? Aggregation, contribution of a b3aggrcon file, an upstream
build...?
* Doesn't the aggregator has checks to ensure that everything can be
installed at once? If not, I'd make it an enhancement request.
* Which feature do you suggest to get rid of to overcome this
installation issue?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev