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

[Hardy Ferentschik]

As much as I see the potential of gradle I don't want to be the one to  
push this forward
right now. A multi-module setup is a minor change in this case.

--Hardy

On Fri, 12 Feb 2010 11:57:17 -0300, Steve Ebersole <steve at hibernate.org>  
wrote:

> Might I suggest y'all look at gradle since this is something you re just
> getting ready to start?
>
> On Fri, 2010-02-12 at 11:55 -0300, Hardy Ferentschik wrote:
>> It seems to me that there are potential other benefits we could gain  
>> from
>> a multi-module
>> setup.
>>
>> Maybe Emmanuel should actually do it, since he loves maven so much ;-)
>>
>> On Fri, 12 Feb 2010 11:46:32 -0300, Sanne Grinovero
>> <sanne.grinovero at gmail.com> wrote:
>>
>> > 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.
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev