Re: [Exist-development] gradle vs maven

[Adam R. <ad...@ex...>]

I did consider in some detail Gradle, Buildr and Ivy+Ant before
settling on Maven.

The main advantage to Gradle is complete flexibility as its written in
programming code i.e. Groovy.
The main disadvantage to Gradle is complete flexibilty and having to
write code in Groovy.

I decided on Maven and not Gradle because -
1) Many more people know Maven than Gradle.
2) The tooling and support for Maven is much much better than Gradle.
3) I didnt want to have to learn Groovy and ship a Groovy run-time
with my application.
4) I think a build system should be declarative, i.e. I want to build
these things, NOT how to build these things. Maven allows you to
describe what things to build, Gradle allows complete flexibility a
bit like Ant but more so, I didnt want to end up in the situation
where we are with Ant now, i.e. maintaining thousands of lines
describing how to build something.

I did actually put together a presentation for the eXist developers
meetup in Prague, but there was not actually enough time to give it
formally - you can find my slides for that here -
http://www.adamretter.org.uk/presentations.xml



On 17 October 2011 07:14, Dmitriy Shabanov <sha...@gm...> wrote:
> Hello,
> It here http://www.gradle.org/
>
> thoughts?
> --
> Dmitriy Shabanov
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb