Comments on: How I stopped worring and learned to love the Maven http://dow.ngra.de/2008/11/20/how-i-stopped-worring-and-learned-to-love-the-maven/ no buzzwords allowed Wed, 10 Mar 2010 17:47:15 -0500 http://wordpress.org/?v=2.9 hourly 1 By: Taisa http://dow.ngra.de/2008/11/20/how-i-stopped-worring-and-learned-to-love-the-maven/comment-page-1/#comment-3646 Taisa Sat, 22 Nov 2008 12:58:25 +0000 http://dow.ngra.de/?p=453#comment-3646 The 2 biggest problem I have with maven is sometimes it's difficult to resolve library dependencies using the maven-dependency-plugin and dfining more complex tasks require you to either write a plugin or call and Ant task wchi is pretty nuts(since I don't believe xml is a programming language). Ivy is more functional in the aspect that's one of the reasons I've been trying out Gradle, a build system that uses Ant, Ivy and allows you to define tasks with groovy. The other reason is groovy is much closer to java than ruby and co, so my programmers don't need to learn an entire new language to modify a build script. I think it's almost ready for serious use(probably around v0.6 or 0.8) but in the meantime were sticking with maven which has been pretty good. The 2 biggest problem I have with maven is sometimes it’s difficult to resolve library dependencies using the maven-dependency-plugin and dfining more complex tasks require you to either write a plugin or call and Ant task wchi is pretty nuts(since I don’t believe xml is a programming language). Ivy is more functional in the aspect that’s one of the reasons I’ve been trying out Gradle, a build system that uses Ant, Ivy and allows you to define tasks with groovy. The other reason is groovy is much closer to java than ruby and co, so my programmers don’t need to learn an entire new language to modify a build script.

I think it’s almost ready for serious use(probably around v0.6 or 0.8) but in the meantime were sticking with maven which has been pretty good.

]]> By: n8 http://dow.ngra.de/2008/11/20/how-i-stopped-worring-and-learned-to-love-the-maven/comment-page-1/#comment-3566 n8 Thu, 20 Nov 2008 22:11:53 +0000 http://dow.ngra.de/?p=453#comment-3566 Wow, that's the most props I've ever gotten for a single method call! But with Buildr it's all about example code (otherwise goodbye weekend afternoon) so I guess that counts for something. The first thing I thought when reading this (I hadn't heard of it) was that Buildr also could get to Maven dependencies through Antwrap. That would be super-slow, but could be useful for pom.xml migration, or even (cached) transitive dependency support. Maven would be the de facto standard for resolving dependencies (with all its ambiguous cases, quirks, bugs, whatever) that other tools could call into rather than try to emulate. Wow, that’s the most props I’ve ever gotten for a single method call! But with Buildr it’s all about example code (otherwise goodbye weekend afternoon) so I guess that counts for something.

The first thing I thought when reading this (I hadn’t heard of it) was that Buildr also could get to Maven dependencies through Antwrap. That would be super-slow, but could be useful for pom.xml migration, or even (cached) transitive dependency support. Maven would be the de facto standard for resolving dependencies (with all its ambiguous cases, quirks, bugs, whatever) that other tools could call into rather than try to emulate.

]]> By: Daniel Spiewak http://dow.ngra.de/2008/11/20/how-i-stopped-worring-and-learned-to-love-the-maven/comment-page-1/#comment-3563 Daniel Spiewak Thu, 20 Nov 2008 19:47:52 +0000 http://dow.ngra.de/?p=453#comment-3563 I'm slowly becoming a fan of Buildr, the Ruby-based drop-in replacement for Maven2. For one thing, the syntax is great (three lines instead of fifty to get a basic Java project up and running). It also lets you drop back to Ruby whenever you need a Turing Complete language (that's part of what drew me away from Ant). It is also *blisteringly* fast. I don't know what it is about Maven which causes it to take so long on simple stuff, but whatever the problem is, Buildr avoids it. It isn't perfect yet (still has some issues with weird Maven repo layouts), but it's getting there. Oh, and thanks to the efforts of Nathan Hamblen, it also has support for JavaRebel: http://www.javaworld.com/javaworld/jw-12-2007/jw-12-outside-the-ide.html?page=4 I still use Ant for most Java stuff, but I have completely switched to Buildr for Scala, and I'm definitely leaning its direction for just about everything else. Should be interesting to see how this "war of the build tools" shapes up and which one ends up reigning supreme. I’m slowly becoming a fan of Buildr, the Ruby-based drop-in replacement for Maven2. For one thing, the syntax is great (three lines instead of fifty to get a basic Java project up and running). It also lets you drop back to Ruby whenever you need a Turing Complete language (that’s part of what drew me away from Ant).

It is also *blisteringly* fast. I don’t know what it is about Maven which causes it to take so long on simple stuff, but whatever the problem is, Buildr avoids it. It isn’t perfect yet (still has some issues with weird Maven repo layouts), but it’s getting there.

Oh, and thanks to the efforts of Nathan Hamblen, it also has support for JavaRebel: http://www.javaworld.com/javaworld/jw-12-2007/jw-12-outside-the-ide.html?page=4

I still use Ant for most Java stuff, but I have completely switched to Buildr for Scala, and I’m definitely leaning its direction for just about everything else. Should be interesting to see how this “war of the build tools” shapes up and which one ends up reigning supreme.

]]>