[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] Publish eclipse-parent and maven-cbi-plugin to Nexus
|
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.
i.e. any bundles we publish for Platform UI go under org.eclipse.ui, not org.eclipse.
I don't see why we would want a different pattern for our releng support modules as we want for our regular maven modules.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
