On a related note, you might want to use the someEclipseGroupId:Bundle-SymbolicName flavor of the Eclipse dependencies.
I have been looking for "official" answers to the "official" Eclipse coordinates question, but haven't found any. From my understanding of a discussion [1] on the dev list, the use of <groupId>someEclipseGroupId</groupId> <artifactId>someEclipseArtifactId</artifactId> is discouraged in favor <groupId>someEclipseGroupId</groupId> <artifactId>Bundle-SymbolicName</artifactId> So in the case of "runtime", you would use org.eclipse.core:org.eclipse.core.runtime instead of org.eclipse.core:runtime. For the Eclipse stuff, there are no relocation poms deployed in the central repo which form a relationship between the someEclipseGroupId:someEclipseArtifactId and someEclipseGroupId:Bundle-SymbolicName flavors. I don't know if that is a good thing or a bad thing. In my projects, I chose to use the someEclipseGroupId:someEclipseArtifactId flavor, and that might have been a mistake. Now I have deployed projects which contain exclusion filters for the someEclipseGroupId:Bundle-SymbolicName flavor. [1] - http://www.nabble.com/What-is-the-official-Eclipse-repo-layout-(was%3A-How-to-use-central-repo-into-an-Eclipse-project-)-td17396298.html#a17396578 -- View this message in context: http://www.nabble.com/Dependency-problem-for-org.eclipse.core%3Aruntime%3A3.3.100-v20070530-tp19327179p19332764.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
