I think the bigger question is... why? Why do they want to abandon Maven? What isn't your build system doing to meet your needs?
Further, as more and more hacks are made to a build system over three years, any system can seem crufty and inappropriate, when the problem is that noone thought through the original changes. I mean, a good build system can be built from shell scripts or make, as can a bad one. The same goes with Maven. Perhaps the right decision is rather to look at your requirements, look at the tools, and see what system fits your organization's needs the best. Our organization came to the conclusion that Maven 2 would suit our needs with a few custom plugins, though Maven 1 did not. However, the largest change we've had is funneling all changes to the build infrastructure through two people. It allows us to keep our modules consistant, which is the largest challenge to a build system. On 1/3/06, Piéroni Raphaël <[EMAIL PROTECTED]> wrote: > Hello, > > after 3 years of using maven, > there is a discussion here at work, > that risk to come back to ant... > > please send me the pointers for using ant versus maven, i can't remember > where to find them... (maven 1 or 2) > > In advance Thank you > > Raphaël > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
