Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gemini-dev] Gemini Maven Repositories: Choosing the Maven GroupId

+1 to use org.eclipse.gemini as the groupId

From: "Nepomuk Seiler" <nepomuk.seiler@xxxxxxxxx>
To: "Gemini and sub-projects developer discussions" <gemini-dev@xxxxxxxxxxx>
Sent: Wednesday, 28 November, 2012 5:48:57 PM
Subject: Re: [gemini-dev] Gemini Maven Repositories: Choosing the Maven        GroupId

+1 to keep org.eclipse.gemini as groupId
Am 28.11.2012 15:16, schrieb Violeta Georgieva:
+1 to keep org.eclipse.gemini as groupId

2012/11/28 Glyn Normington <gnormington@xxxxxxxxxx>
Hi Juergen

Sounds reasonable to me. I am planning to use a groupid of org.eclipse.gemini or org.eclipse.gemini.blueprint for Gemini Blueprint.

If you find a reliable way of populating the Gemini Maven repository, I would love to hear about it. At the moment, I am expecting to have to zip up a temporary repository and then unzip it over the top of the Gemini Maven repository - ample opportunity for slips. I think Maven is supposed to automate this kind of thing isn't it?...

Regards,
Glyn

On 28 Nov 2012, at 10:03, Kissner, Juergen wrote:

Hi,
 
Gemini DBAccess is about to get its Maven repository too (finally).
 
Looking at the current Gemini Maven repository at gemini/mvn, the Gemini projects JPA, Management and Naming use the Maven groupId “org.eclipse”. It is only Gemini Web that has the groupID “org.eclipse.gemini”.
 
However, looking at maven central, most eclipse projects seem to have a groupId  “org.eclipse.<project>”:
http://search.maven.org/#browse|1428323731
In fact, if all projects there had been using “org.eclipse” things would look rather messy.
 
DBAccess will start with seven artifacts; every newly supported DB platform will add an additional one.
 
I would therefore like to use “org.eclipse.gemini” or even “org.eclipse.gemini.dbaccess” for the groupId of the DBAccess maven artifacts.
 
Considering Gemini Web, I would suggest groupId “org.eclipse.gemini”. I know that the Gemini projects do not necessarily have to share the same group id, but it would be more homogeneous and consistent.
 
Best Regards,
   Juergen
_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev




_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

Back to the top