Re: [cbi-dev] Publish eclipse-parent and maven-cbi-plugin to Nexus

[Mickael Istria <mistria@xxxxxxxxxx>]

On 09/11/2012 09:02 PM, Paul Webster wrote:

On Tue, Sep 11, 2012 at 2:51 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

I advise first changing groupId (to org.eclipse.platform or org.eclipse.platform.releng) and then publish to Nexus. So it won't collide with current "eclipse-parent" plugin. Once it is published and used by platform build, we may be able to think about some refactorings to make it more useful. For other projects, groupId starts with org.eclipse.<projectName> (just as package name), platform should follow this convention instead of introducing a org.eclipse.releng.

We're not the platform project, we're the Eclipse Project (a legacy of when there was only one project :-)

But because that puts us at org.eclipse or org.eclipse.eclipse each project (within the Eclipse Project) was to use the first 3 segments as its groupId.  org.eclipse.releng is a component, as is org.eclipse.ui, org.eclipse.jdt, org.eclipse.pde, org.eclipse.equinox, etc.

That said, it makes sense to use org.eclipse.releng. But it's not a very explicit name IMHO, and it can lead to the conclusion that this pom may be helpful to other projects. What about org.eclipse.platform-releng ?

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets