+1 on the approach, do you already have plans of many modules?
2011/3/11 Emmanuel Bernard <emman...@hibernate.org>: > 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 :) > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
