Re: [gemini-dev] Gemini Maven Repositories: Choosing the Maven GroupId

[michael keith <michael.keith@xxxxxxxxxx>]

Hi Juergen,

Thanks for suggesting this. When we picked the group id we just used what some other projects were using at the time and it was not necessarily the best choice. I would be fine to switch to org.eclipse.gemini in Gemini JPA.

-Mike

On 28/11/2012 5:03 AM, 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