On 24 July 2012 18:41, Gordon Sim <[email protected]> wrote: > On 07/23/2012 09:38 PM, Robbie Gemmell wrote: > >> I wouldn't particularly be in favour of Ant+Ivy for proton. >> > > Any particular reason? > > Because I think more people (excluding some of us, obviously) would prefer that we use maven instead.
> I must be old or stupid (or both!) because I can't understand why people > like maven. Admittedly I haven't used it for a long time and the usability > may have improved. However my recollection is of more frustration than I > have ever experienced with a 'build system'. > > I think primarily people like it because of the somewhat standardised lifecyle across various projects mean they can just pick them up more easily, and an increasing amount of tooling caters to maven usage, making it easier to integrate a variety of utilities into builds without rolling your own integration. I guess there is also the consideration that at some point it became more popular *because* it became popular (you know, like most things Apple make). > Even philosophically it seemed wrong to me - I want to compile my changes > and it goes off looking for any updates to jar files the project or the > tool itself might use. That sort of system update seems to me like it > should be an entirely separate step. > > I do hear what you are saying here, though I dont object to the extent it seems some do. The versions can all be locked down so that its really just checking if you changed verisons since the last build. Somthing that our main java build has also been doing ever since I added Ivy to it. > At present sadly I don't have the time to spend on proton-j that I would > like, so my opinion should not be given much weight if the preference for > maven is widespread amongst real users and developers. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
