Hi, /delurk
On 26-3-2011 21:13, Terence Parr wrote: > I'm actually thinking of dumping use of mvn for build purposes. i don't like > its complexity and dir structure. what used to be v4 (complete rewrite of > antlr) used ant nicely and easily. we can still have a mvn plugin of course. Have a look at gradle (www.gradle.org). Currently converting 16K lines of maven build to gradle and it looks like the whole build can be captured in a few 100 lines of gradle code. Maven has so much convention that it is close to unusable. With gradle silly restrictions like one artifact per pom are gone. And if you can't do it with dependencies your just script it, or use an ant task. Or write your own plugin (you can even write the plugin inline) Disadvantages so far, its groovy, so syntax is often a bit fuzzy. And sometimes it's hard to figure out how to do something (mostly advanced stuuf, there's a bit of a learning curve but not as steep as antlr :) so you should be ok). Advantages, it's a tool with a 'we get your job done' attitude, not the mvn choke in our conventions, and the mvn crappy plugins. Mailing list is very helpfull as well. You can generate maven/ivy artifacts with gradle and deploy them as well. There are some antlr plugins for gradle, no clue as to the quality. But it should be really easy to integrate antlr (and have really good up to date checks) Gradle builds incremental out of the box. There are a lot of build examples, since a lot of open source projects are switching to gradle. Cheers, Ric /lurk _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
