On Tue, 16 Mar 2010 15:38:40 -0300, Emmanuel Bernard <emman...@hibernate.org> wrote:
> What's the list of all potential modules? Then let's see if we want to > minimize some or create bundles > > hibernate-search-core Here I had in mind to use just hibernate-search so that the main artifact keeps its name. > hibernate-search-hibernate Not sure what you envision to go in there. I did not have this on the list and I am not quite sure what would be in there. > hibernate-search-jpa This is the one I want to avoid, since we really don't have any specific JPA code. The only use we have of JPA at the moment is that we use @Id as document id in case @DocumentId is not specified. This use is, however, via reflection and we never actually load any javax.persistence classes. In the testsuite we are making of course heavy use of JPA to build our tests. I might have an idea on how to deal with this. I don't think we need this module. > hibernate-search-jms > hibernate-search-jgroups > hibernate-search-infinispan I guess it makes sense to start creating modules for the different clustering solutions. I think this three modules will also make it more transparent what you need if you want to use clustering > hibernate-search-util I guess we could create this module, but I would like to avoid it. I guess I would then rather split out the test into a hibernate-search-testsuite > hibernate-search-testutil Ok > hibernate-search-perftest I guess we could do this as well. > anything else? What did we decide on the solr analyzer framework? --Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
