Same here, I don't want to use freestyle jobs to maven as I base my releases to the m2-release plugin of Hudson (yes I know about the freestyle release plugin, but it doesn't fit exactly to the needs of a maven release)
I also think that having different versions of maven in development and CI is not the best practice as it might give headaches to the developers if there is a mis-alignment between those two. I'm not concerned about the stability of m3-beta, the IT tests are doing an excellent job to keep compatibility, but I need the integration features of m2 to go ahead, so I'll also wait for the hudson m3 support to migrate. Dimitris 2010/5/7 Frederic Camblor <fcamb...@gmail.com> > [Joke] > Hey ! Marty McFly should be able to see in the future with its dolorean ! > By doing this, you should know when m3 will be released :-) > [/joke] > > Joke apart, using Freestyle jobs doesn't allow to use maven oriented plugin > in the builds (like release hudson plugin). > To my part, I won't migrate while hudson won't provide alignment on m3. > > Frédéric > > On Fri, May 7, 2010 at 5:20 PM, Wayne Fay <wayne...@gmail.com> wrote: > > > > In Hudson I can currently only set up a Maven2 project - is this also > > > working with Maven 3 oder do we have to wait till the maven plugin in > > > hudson > > > is updated ? > > > > You could try building with M2 on Hudson and use M3 on your > > developer's desktops (assuming you're doing nothing weird, it should > > mostly work OK). Or if you found issues, just use M2 everywhere for > > now, then upgrade in a few months. > > > > Wayne > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
