I have a feeling a lot of similar pain to hibernate - as a lot of the needs are the same (multiple modules, possibly different releases etc).
On Mon, Jul 12, 2010 at 9:03 AM, Mark Proctor <[email protected]> wrote: > On 11/07/2010 23:55, Michael Neale wrote: > > I think you mean gradle - but yes, that makes sense. > > 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. > > As a consumer of libraries, I like having declarative dependencies, no > matter what my build system is, so that is a good thing. > > 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. > > 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. > > 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 ;) > > 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. > > Mark > > > Maven 3 promises to be compatible - so that is an improvement over maven1 > (not sure if many remember that... oh the horror). > > On Mon, Jul 12, 2010 at 8:23 AM, Mark Proctor <[email protected]>wrote: > >> I'm happy to let the hibernate people guinee pig Grails. Initially >> we'll move to maven 3 (as it's backwards compatible), and for the moment >> maven is still what most people are familiar with. >> >> We'll be restructuring the build over time and if maven 3 doesn't do >> what we need and/or hibernate people are reporting amazing results with >> no sign of improvements to maven, then we can evaluate Grails. >> >> Mark >> >> >> On 11/07/2010 14:55, Geoffrey De Smet wrote: >> > Steve makes some good, valid points on that blog about Maven 2. >> > I get the feeling that Maven 3 fixes a lot of those problems and the >> > maven 3.1 promises a lot too. >> > At Devoxx 2009 I saw 2 presentations: >> > - Gradle (the lead, forgot his name): showed a build of a one module >> > project with one source file - and it was fast. All in all, Gradle felt >> > like a toy (I must be wrong since the Hibernate guys are serious). >> > - a Maven 3 (the lead, Jason) presentation: he basically went over all >> > the things I hate about maven 2 and stated that maven 3 or 3.1 would fix >> > them while remaining backward compatible. He showed a large >> > multi-project build with tons of sources files and it was relatively >> fast. >> > >> > It will be very interesting to see how hibernate's experimentation with >> > Gradle goes and how the maven guys react. >> > >> > >> > Nevertheless, I am convinced that most of the problems in our build are >> > fixable, by cleaning up our build: >> > https://jira.jboss.org/jira/browse/JBRULES-2504 >> > If I get some time for that, I 'd love to pull the effort to fix those >> > issues. >> > >> > With kind regards, >> > Geoffrey De Smet >> > >> > >> > Salaboy schreef: >> >> 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 >> >> >> >> - CTO @ http://www.plugtree.com >> >> - MyJourney @ http://salaboy.wordpress.com >> >> - Co-Founder @ http://www.jbug.com.ar >> >> - Mauricio "Salaboy" Salatino - >> >> >> >> On Jul 9, 2010, at 4:25, tolitius<[email protected]> wrote: >> >> >> >>> Before you move to Maven 3. There is still a chance to do the right >> thing: >> >>> >> >>> http://community.jboss.org/wiki/Gradlewhy >> >>> >> >>> one of the JBoss projects ( Hibernate ) already realized that. Time >> for >> >>> Drools to do to. >> >>> >> >>> /Anatoly >> >>> -- >> >>> View this message in context: >> http://drools-java-rules-engine.46999.n3.nabble.com/Dropping-Maven-for-Gradle-tp727052p953763.html >> >>> Sent from the Drools - Dev mailing list archive at Nabble.com. >> >>> _______________________________________________ >> >>> rules-dev mailing list >> >>> [email protected] >> >>> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> _______________________________________________ >> >> rules-dev mailing list >> >> [email protected] >> >> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> >> > _______________________________________________ >> > rules-dev mailing list >> > [email protected] >> > https://lists.jboss.org/mailman/listinfo/rules-dev >> > >> > >> >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev >> > > > > -- > Michael D Neale > home: www.michaelneale.net > blog: michaelneale.blogspot.com > > > _______________________________________________ > rules-dev mailing > [email protected]https://lists.jboss.org/mailman/listinfo/rules-dev > > > > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev > > -- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com
_______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
