<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/07/2010 23:55, Michael Neale wrote:
<blockquote
cite="mid:AANLkTikF6qAiy-J0ka_SlpXb1ebCRwezCjn6EaOE1ovR@mail.gmail.com"
type="cite">I think you mean gradle - but yes, that makes sense.
<div><br>
</div>
<div>There were others I was fond of - buildr was one - as far as
I know, the nice things about all these "alternative" tools is
that they at the least reuse the maven repositories and meta
data - so it isn't starting from scratch. </div>
<div><br>
</div>
<div>As a consumer of libraries, I like having declarative
dependencies, no matter what my build system is, so that is a
good thing. </div>
<div><br>
</div>
<div>I think the drools build is pretty much as complex as
hibernate - more so even - drools has a few stand alone
components that have quite fiddly build steps (which still
probably aren't fully automated), things like GWT, building cut
down app servers etc... so it is worth watching closely how
hibernate do. </div>
<div><br>
</div>
<div>Myself - I know that MarkP has struggled for years with
maven, and won most battles - so the day I see mark switch to
gradle/whatever, is the day I would probably switch. <br>
</div>
</blockquote>
Build systems can suck time like nothing else, I've wasted so much
time in the past. So in general the less time I spend working on the
build the better, and at the moment it's not taking up a lot of
time, so I have to get a strong itch to swap one pain for another ;)<br>
<br>
We will be splitting up the build going forward, so we'll see how
much pain we go through there and whether it creates a strong enough
itch.<br>
<br>
Mark<br>
<blockquote
cite="mid:AANLkTikF6qAiy-J0ka_SlpXb1ebCRwezCjn6EaOE1ovR@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>Maven 3 promises to be compatible - so that is an improvement
over maven1 (not sure if many remember that... oh the horror). </div>
<div>
<div><br>
<div class="gmail_quote">On Mon, Jul 12, 2010 at 8:23 AM, Mark
Proctor <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;"> I'm happy to let the hibernate
people guinee pig Grails. Initially<br>
we'll move to maven 3 (as it's backwards compatible), and
for the moment<br>
maven is still what most people are familiar with.<br>
<br>
We'll be restructuring the build over time and if maven 3
doesn't do<br>
what we need and/or hibernate people are reporting amazing
results with<br>
no sign of improvements to maven, then we can evaluate
Grails.<br>
<font color="#888888"><br>
Mark<br>
</font>
<div>
<div class="h5"><br>
<br>
On 11/07/2010 14:55, Geoffrey De Smet wrote:<br>
> Steve makes some good, valid points on that blog
about Maven 2.<br>
> I get the feeling that Maven 3 fixes a lot of
those problems and the<br>
> maven 3.1 promises a lot too.<br>
> At Devoxx 2009 I saw 2 presentations:<br>
> - Gradle (the lead, forgot his name): showed a
build of a one module<br>
> project with one source file - and it was fast.
All in all, Gradle felt<br>
> like a toy (I must be wrong since the Hibernate
guys are serious).<br>
> - a Maven 3 (the lead, Jason) presentation: he
basically went over all<br>
> the things I hate about maven 2 and stated that
maven 3 or 3.1 would fix<br>
> them while remaining backward compatible. He
showed a large<br>
> multi-project build with tons of sources files
and it was relatively fast.<br>
><br>
> It will be very interesting to see how
hibernate's experimentation with<br>
> Gradle goes and how the maven guys react.<br>
><br>
><br>
> Nevertheless, I am convinced that most of the
problems in our build are<br>
> fixable, by cleaning up our build:<br>
> <a moz-do-not-send="true"
href="https://jira.jboss.org/jira/browse/JBRULES-2504"
target="_blank">https://jira.jboss.org/jira/browse/JBRULES-2504</a><br>
> If I get some time for that, I 'd love to pull
the effort to fix those<br>
> issues.<br>
><br>
> With kind regards,<br>
> Geoffrey De Smet<br>
><br>
><br>
> Salaboy schreef:<br>
>> I think that after the release it would be
nice to research on this kind of things. And now if
jboss has another framework that uses gradle, probably
will be easier to migrate<br>
>><br>
>> - CTO @ <a moz-do-not-send="true"
href="http://www.plugtree.com" target="_blank">http://www.plugtree.com</a><br>
>> - MyJourney @ <a moz-do-not-send="true"
href="http://salaboy.wordpress.com" target="_blank">http://salaboy.wordpress.com</a><br>
>> - Co-Founder @ <a moz-do-not-send="true"
href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br>
>> - Mauricio "Salaboy" Salatino -<br>
>><br>
>> On Jul 9, 2010, at 4:25, tolitius<<a
moz-do-not-send="true"
href="mailto:webakaunt@gmail.com">webakaunt@gmail.com</a>>
wrote:<br>
>><br>
>>> Before you move to Maven 3. There is
still a chance to do the right thing:<br>
>>><br>
>>> <a moz-do-not-send="true"
href="http://community.jboss.org/wiki/Gradlewhy"
target="_blank">http://community.jboss.org/wiki/Gradlewhy</a><br>
>>><br>
>>> one of the JBoss projects ( Hibernate )
already realized that. Time for<br>
>>> Drools to do to.<br>
>>><br>
>>> /Anatoly<br>
>>> --<br>
>>> View this message in context: <a
moz-do-not-send="true"
href="http://drools-java-rules-engine.46999.n3.nabble.com/Dropping-Maven-for-Gradle-tp727052p953763.html"
target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Dropping-Maven-for-Gradle-tp727052p953763.html</a><br>
>>> Sent from the Drools - Dev mailing list
archive at Nabble.com.<br>
>>>
_______________________________________________<br>
>>> rules-dev mailing list<br>
>>> <a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
>>> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
>>
_______________________________________________<br>
>> rules-dev mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
>> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
>><br>
> _______________________________________________<br>
> rules-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Michael D Neale<br>
home: <a moz-do-not-send="true"
href="http://www.michaelneale.net">www.michaelneale.net</a><br>
blog: <a moz-do-not-send="true"
href="http://michaelneale.blogspot.com">michaelneale.blogspot.com</a><br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>