|Re: [CDO] IAdaptable name clash [message #1693028 is a reply to message #1692984]
||Tue, 21 April 2015 10:34
| Andras Peteri
Registered: January 2010
Release train projects (i.e. those that contribute to the release train) must not consume their upstream dependencies
from the release train. A good example for what can happen is Mylyn; they built their M6 against Platform M5 and didn't
recognize that the Platform removed some internal code in M6. So Mylyn built fine, but when they contributed their build
to the release train, it didn't work anymore.
Thanks for the explanation, it is completely reasonable. But now I'm wondering how CDO or other projects can build on this functionality in its preliminary state, and what repository is providing the newer equinox.common bundle in CDO's setup model? I couldn't tell just by looking at the repository list.
I have started provisioning a workspace from scratch, and the setup log now says that http://download.eclipse.org/eclipse/updates/4.5milestones will be included in the list of repositories to use, which I don't remember seeing earlier (I can only find a reference to it in build.rmap in the workspace). My guess is that if not set explicitly, it is up to the P2 resolver's discretion which version of the bundle it ultimately chooses, if alternatives are available and the version requirements are otherwise met.
Powered by FUDForum
. Page generated in 0.01529 seconds