> > I dislike "orm" as it's too generic, we don't want to imply to support any > orm. > > We already mention hibernate in the group id properly identifying the > team working on it, so if the kernel of H.Search doesn't need H.Core > as it will drop the hibernate-core depencency, we could call the core > module "search", and keep "hibernate-search" as the integration module > providing the current eventlistener functionality. Everyone using > "Hibernate Search" will still depend on the "hibernate-search" > artifact anyway so we're not loosing any branding. > > As an example: Infinispan Query would not depend on "hibernate-search" > but on "org.hibernate.search:search", being this only the search > engine, produced by the Hibernate Search project. > > So, proposal: > groupId: > org.hibernate.search > > assembly artifactId: > search-assembly > kernel artifactId: > search > parent: > search-parent > hibernate integration: > hibernate-search > infinispan integration > infinispan-search (is currently hibernate-search-infinispan)
Well you can't use Hibernate as a synonym for Hibernate Core. It goes against what I've been working for in the last 5 years :) BTW all artifactIds have been named hibernate-search-* I'm open to drop it but I wonder why we did that in the first place. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
