Re: [hibernate-dev] Move Search to a multi-module build

it's ok for me; the best benefit I expect is to split the testssuite and clean that, opening the doors to a performance&stress testsuite. Also the Solr "optional" dependencies should be actually mandatory if you use the analyzerdefs, so this could eventually be moved to a separate search module; that helps in dependecy management for users. Eventually other optional dependencies could follow - not sure the support for JPA won't be easy to split out but at least you would have options to do so if you wished. Similar story for other dependencies like JGroups backend, soon Infinispan DirectoryProvider, etc.. maybe even a contrib are for experimental backends and so on. I never had issues with the archetype? Eclipse ignores it. Sanne 2010/2/12 Emmanuel Bernard <emmanuel(a)hibernate.org&gt;: > Is the quickstart archetype really needed? > On my side, I always exclude it as it goes in my way. > > On 12 févr. 2010, at 15:25, Hardy Ferentschik wrote: > >> Hi, >> >> For HSEARCH-459 I would like to move Search to a multi-module setup >> (similar to Validator). >> This way the archetype sources will actually always get compiled and are >> less likely to get outdated. >> >> I think we talked before about potential benefits of having a multi-module >> build for Search. Any objections >> if I go ahead with this? >> >> --Hardy >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev >