> 1. Does that mean that the poms we write would look exactly same as how > they > would have looked during maven 2.x days ? >
There are no changes to the pom. A pom that works with Maven 3.0.x should work with Maven 2.x (with the possible exception that some specific plugin might not work with some Maven version). 2. "3 will complain if you did not specify versions in the plugins" > I guess, this applies only to the plugins that ate *not* specified in teh > superpom ( core plugins ) ? > No, you should specify a version for all plugins (either in your pom or in a parent pom). The ones in the super-pom are just a safety net. /Anders > > > --sony > > > > > > On Fri, Apr 15, 2011 at 1:06 AM, Tom Eugelink > <[email protected]>wrote: > > > If you do nothing fancy in your plugins then you should be able to > migrate > > to 3 without changes to the plugin. 3.0 is mainly a refactoring of the 2 > > code and tries to remain as much backwards compatible as is possible. So > no, > > yes, no. > > 3 will complain if you did not specify versions in the plugins, so that > is > > something to pick up. > > > > > > > > > > > > On 15-4-2011 04:34, Sony Antony wrote: > > > >> We have been using mvn 2.1 for a while and we have understood it fairly > >> well. > >> Recently we decided to move to 3.x,( mainly for teh parallel build > feature > >> with the -T switch ) > >> > >> But we find teh documentation difficult to come by. Googling didnt dig > up > >> any tutorial or guides for 3.0 specific features. > >> Specifically, we have the following fundamental questions. Will be very > >> grateful if somebody could answer these. > >> > >> 1. I read about the changes for the pom.xml in 3.x. Does that mean that > I > >> should change my poms, even if I m not using any features specific to > 3.x. > >> ( > >> Maybe I should change the namespace from > >> http://maven.apache.org/POM/4.0.0 to > >> something newer ? ) > >> 2. When I built a simple project, all of teh plugins that got > >> automatically > >> downloaded from http://repo1.maven.org looked pretty much like the > >> plugins > >> used by maven 2.x. Does that mean that most of the plugins and > >> repositories > >> I would be using will be exactly same as maven 2.x ? > >> 3. Even teh super pom looks teh same in maven 3.x ( verified using > >> help:effective-pom ). Are we supposed to oevrride any of teh versions in > >> the > >> superpom for the core plugins, so as to get the ones that would work > with > >> maven 3.x ? ( probably to get the latest thread safe versions ? ) > >> > >> Thank you for reading. > >> > >> > >> > >> --sony > >> > >> > > > > -- > > > > *Tom Eugelink* > > Senior software engineer > > +31 (0)6 - 47 93 85 92 > > [email protected] <mailto:[email protected]> > > *KnowledgePlaza <http://www.knowledgeplaza.nl>* > > Sutton 15 > > 7327 AB Apeldoorn > > Tel: +31 (0)55 - 526 3887 > > Fax: +31 (0)55 - 526 3950 > > [email protected] <mailto:[email protected]> > > Disclaimer: The information contained in this message is for the intended > > addressee only and may contain confidential and/or privileged > information. > > If you are not the intended addressee, please delete this message and > notify > > the sender; do not copy or distribute this message or disclose its > contents > > to anyone. > > > > > > > > > > > > > > > > > > >
