[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[buckminster-dev] Major branching
|
Hi,
With the 3.6M3, the p2 team made some significant changes. Classes like Version and VersionRange were moved from their
core bundle to the metadata bundle. This forces us to immediately branch several projects.
If you have things checked out in one of these projects, you have two options:
1. If your changes are targeted to 3.6.
Update your target platform (the build.rmap in our releng is up-to-date). Then just update your projects to make
everything build again.
2. If your changes are targeted for 3.5.x
Don't check-in at this point. Instead, switch branch. I.e. first you switch your branch, then you check in. Not the
other way around.
Here is a list of affected projects:
org.eclipse.buckminster.aggregator
org.eclipse.buckminster.aggregator.edit
org.eclipse.buckminster.aggregator.engine
org.eclipse.buckminster.aggregator.engine.maven
org.eclipse.buckminster.ant
org.eclipse.buckminster.core
org.eclipse.buckminster.cvs
org.eclipse.buckminster.installer
org.eclipse.buckminster.maven
*org.eclipse.buckminster.pde
org.eclipse.buckminster.pde.ui
org.eclipse.buckminster.rmap.psf
*org.eclipse.buckminster.ui
org.eclipse.buckminster.ui.dependencyvisualizer
* == branched earlier.
Regards,
Thomas Hallgren
