Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Planning to make .../releases/kepler be M4 only

Most of you know, that we normally keep 3 milestones in our common repository, as a composite.
This works as  long as no one removes a feature or a feature is mistakenly "down versioned".

But, I have detected a problem with doing that this time. See
Bug 397033 - Acceleo has conflicting dependency in M2, M3, M4 composite Kepler repo

The easiest fix at this point, for common repo is just to make the common repo be M4 only, to avoid the "conflicting dependencies", though it might be a sign of some other problem with the contribution.  Please comment in the bug, if anyone was really looking forward to testing "roll back" or "performance" this milestone :) or knows of a better fix (keeping in mind, its too late to "fix" the repo it self, just for this).

With just M4 enabled, I was able to select and "install everything" ... but ... did eventually get an error about
An error occurred while installing the items
session context was:(profile="" phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.php.core.source 3.1.1.201209101312, action="">
The artifact file for osgi.bundle,org.eclipse.php.core.source,3.1.1.201209101312 was not found.

Not sure if that's reproducible, some contribution is wrong, or a sign some mirror is misconfigured, or where it comes from. Just reporting it here to encourage all "test early, test often" :)

 


Back to the top