As far as I can tell, Maven 3 primarily changes things behind the scenes. There aren't a lot of new features. It is just cleaning things up for planned new features in 3.1, so there isn't a lot of incentive to change--particularly if everything is working on Maven2 right now. It probably makes sense to at least wait at least until Hudson offers a Maven3 plugin.
Mark On Mon, Oct 25, 2010 at 2:36 AM, Igor Drobiazko <[email protected]>wrote: > I prefer to stay with maven. We don't need to switch to Maven3. Right now > we > have a working build based on Maven 2. Why switching? > > On Mon, Oct 25, 2010 at 8:26 AM, Joachim Van der Auwera <[email protected] > >wrote: > > > Personally I love maven. > > Though maven's site plug-in may indeed be more trouble than it is worth. > > Not really surprising considering that it has not seen a proper release > in > > years (and the api changed in a couple of the (very infrequent) beta > > releases). > > > > Joachim > > > > > > On 10/23/2010 01:41 AM, Howard Lewis Ship wrote: > > > >> I'm using Maven 3.0 (perhaps I should downgrade). > >> > >> I changed the master POM to use version 2.1.1. > >> > >> Oh, this doesn't look promising: > >> https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html > >> > >> Grinding through it, wish me luck. Time to switch to Gradle! > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de >
