| [CDO] IAdaptable name clash [message #1692777] |
Sat, 18 April 2015 03:57  |
Eclipse User |
|
|
|
Hi,
After updating my local CDO development environment (on master), and re-running Setup tasks, I started getting the following compile error message from multiple UI projects:
"Name clash: The method getAdapter(Class<T>) of type ContainerView has the same erasure as getAdapter(Class) of type WorkbenchPart but does not override it" (ContainerView.java)
According to the affected projects' "Plug-in Dependencies" container, they all get the non-generic version of IAdaptable from org.eclipse.equinox.common_3.6.200.v20130402-1505; the lower bound of required org.eclipse bundle version ranges in their manifests allows this. They depend on org.eclipse.ui and/or org.eclipse.core.runtime that in turn depends on org.eclipse.equinox.common. The corresponding plug-in versions in my target platform are:
* org.eclipse.ui: 3.106.1.v20141002-1150
* org.eclipse.core.runtime: 3.10.0.v20140318-2214
* org.eclipse.equinox.common: 3.6.200.v20130402-1505
What should be done to get the workspace projects to compile? I assume that at runtime, these set of plugins would actually work because of type erasure.
|
|
|
|
|
|
| Re: [CDO] IAdaptable name clash [message #1693028 is a reply to message #1692984] |
Tue, 21 April 2015 06:34  |
| Eclipse User |
|
|
|
Hi Eike,
Quote: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.
--
András
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04965 seconds
Home
I thought that ${cdo.target.platform} controls both the project's as well as the parent Targlet's repository list, but I missed ${eclipse.target.platform} in the workspace.setup model. Thanks for your help!