By bloid
via warneronstine.com
Published: Jul 06 2008 / 17:14
First, let me say, I like Maven - a lot. I’ve liked the idea, if not the execution, since 1.0 (yes, I know there is some serious bad blood for the implementation of 1.0, and yes I still liked it). But I’ve recently run into some irritating problems with Maven that would again, I think, require a major reworking of what it does.
Comments
joecoder replied ago:
Voted down primarily for having a title that sucks given the content of the article. The content itself is a rambling rant with reader having little idea why the author decided to use Gradle as his build system of choice over the alternatives.
bwtaylor replied ago:
There are serious problems with maven, and lack of support for polyglot programming is a big one. This is the first time I've heard of gradle, and it seems promising.
mkleint replied ago:
-1, not the first time i see gradle parasiting on maven. please try to avoid using subjects that suggest that one era is over (maven) and new messiah has arrived (gradle). Thanks.
noahz replied ago:
-1 for FUD. Brian Fox has posted a reply in his blog:
http://blogs.sonatype.com/brian/2008/07/06/1215403020000.html
Also "lack of support for polyglot programming" - care to be more specific? Maven 2 supports embedded Ant scripts, within which you can execute anything. Plus there are dozens of plugins in the primary repository and at CodeHaus. Google harder.
Voters For This Link (12)
Voters Against This Link (9)