[hibernate-dev] groupId vs artifactId

Emmanuel Bernard emmanuel at hibernate.org
Fri Mar 11 13:52:22 EST 2011


Today we have the following approach for most of our projects

groupId: org.hibernate
artifactId hibernate-search-parent, hibernate-search etc

Since I'm working on the ogm packaging, I wonder if we should do something like

groupId: org.hibernate.ogm
artifactId hibernate-ogm-parent, hibernate-ogm-core etc

or even

groupId: org.hibernate.ogm
artifactId ogm-parent, ogm-core etc

thoughts? I don't mind the existing approach except that the org/hibernate directory is getting crowded, we are too prolific :)



More information about the hibernate-dev mailing list