I usually prefer to use ANT and though I haven't used it, Ivy looks to be a nice balance between Maven dependency management and ANT flexibility. I have also used Maven, and once things are setup, I usually don't have too much trouble with it.
In the end, it doesn't matter that much to me, but I would be +1 to ANT/Ivy and +0 to Maven. -Matt On 4/7/11 8:11 AM, "Ross Gardler" <[email protected]> wrote: >On 07/04/2011 12:30, Ate Douma wrote: >> On 04/07/2011 12:02 PM, Okke Harsta wrote: >>> As stated by Niels we from SURFnet have a strong preference for Maven >>> (also because Shindig uses maven and it makes distribution of the >>> deliverables very easy). I'm willing to do the maintenance and to act >>> as the maven expert if there is need for this... Having said this I >>> must admit I'm not very familiar with Ivy so that might explain my >>> preference;-) > >... > >> Ivy I don't know much about, other than having to use it to build >> Wookie. I don't particular like the limited Eclipse IDE (IvyDE) support >> but as a non-expert that very well might be because of my lack of >> experience. > >(I know ANT + Ivy quite well, so I'll only comment on that) > >I think IDE integration is a fair criticism of ANT + Ivy. > >It's one of the penalties of not having a single way of doing things. >It's a flexibility vs convenience trade off. > >> I'd like to know how the Gradle support is for ASF specific requirements >> like artifact and distribution building/validating (rat, etc.) and >> deployments? >> And the same question I have for Ant/Ivy in general. > > From an ANT point of view it's easy to do pretty much anything you want >in ANT. It's more of a build programming environment than a way of doing >things. > >Maven works out of the box, ANT needs customising for specific >environments. EasyAnt (and by the sounds of it Gradle) aim to provide >the maven style "do it this way" recipes. > >> One thing I'd like to add though is that for artifact release and >> deployment I strongly suggest we at least use the Maven Central >> repository (e.g. as Maven artifact) to support end users to integrate >> and use Rave from within Maven based projects. >> AFAIK both Ivy and Graddle could or should be able to do so, right? > >Yes, Ivy uses maven repos (and thus I assume Gradle does). > >Ross
