Trust me, M2 is way more easy then M1 once you grabb the bases concepts. I suggest you to look at M1 maybe just to get a basic grab on those concepts, then switch to M2 for the technical part. The M2 getting started guide is a pretty good introduction and this mailing list is a very good help in case you have problems. Plus, like other have already pointed, a lot of docs is underway. My advice is don't be affraid to go straight to Maven 2, it's worth it and so easy compare to Ant and even Maven 1.
On 1/4/06, Mayorgaadame, Alex <[EMAIL PROTECTED]> wrote: > +1 On releasing that M2 book ASAP =) > > Happy 2006 to all you Maven people. Keep evangelizing!! > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 04, 2006 2:40 AM > To: 'Maven Users List' > Subject: RE: M1 or M2? > > > Thanks Babak. WRT m2 documentation it's already better than m1. However > we're also writing a m2 book. It'll be made available online. We should have > a first release of it in Q1 2006. > > WRT migrating to m2 yes it's easy to do that from m1 provided you follow the > best practices like having a minimal maven.xml file... The hard part is > moving from Ant to Maven because you need to restructure your directory > structure into small subprojects. But if you're on m1 it means you've > already done that and this doesn't change when you move to m2. > > -Vincent > > > -----Original Message----- > > From: Babak Farhang [mailto:[EMAIL PROTECTED] > > Sent: mercredi 4 janvier 2006 07:16 > > To: Maven Users List > > Subject: Re: M1 or M2? > > > > Thanks for encouraging Maven2! > > > > I must say, though, that you didn't address my "Will I suffer?" question > > :-) > > > > I just checked out *Maven: A Dev's Notebook* which is slightly dated > > and based on Maven1. Nice, fairly well-organized, spoon-fed info in > > that book which I hope is more or less applicable to Maven2, as well. > > > > Reading some of the user feedback on reviews about Maven2 (e.g. see > > http://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven-p3.html ) > > I thought it might be wiser if I first learnt Maven1. > > > > > .. If you want to suffer then > > > delve into writing Jelly plugins in Maven1. ;) Maven2 is a beautiful > > > thing... > > > > I'm sure it's beautiful. Really! I'm hoping not to need to write any > > plugins, though. I'm not a build engineer: I'll be using Maven mostly > > because it makes developing apps easier... > > > > So for now, as a newbie, I'll stick to Maven1 until there is better > > documentation out there for Maven2. I *did* try Maven2 along w/ its > > documentation, but for now, here's my advice to other newcomers: > > > > The path to m2 is through m1. > > > > Or ye shall suffer needlessly, as I have... :-) > > > > If I follow the *best practices*, it seems, I should be able to > > migrate relatively painlessly to M2. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
