Everybody thinks it's a good idea so I went for it.
welcome org.hibernate,ogm
@Sanne, you mean modules for OGM? At least one per NoSQL.
On 11 mars 2011, at 20:52, Sanne Grinovero wrote:
> +1 on the approach,
>
> do you already have plans of many modules?
>
> 2011/3/11 Emmanuel Bernard :
>> Tod
+1 on the approach,
do you already have plans of many modules?
2011/3/11 Emmanuel Bernard :
> 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
2011/3/11 Hardy Ferentschik
The artifactId should stay, however, hibernate-ogm-core. Remember the
> artifactId determines the name of the jar file. I prefer
> hibernate-ogm-core over ogm-core.jar.
>
+1 for this approach. This style is also followed by the Seam modules, e.g.:
org.jboss.seam.vali
+1 If we would have started this earlier, we would have a much nicer
namespace under
https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/
Obviously we cannot get rid of/change the existing structure by changing
the groupIds of existing projects, because we have to ke
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-
