Did you roll the maven dependencies back to maven 2.2.1 as the v-m-p has the following contracts
1.x requires maven 2.0.6+ 2.x requires maven 2.2.1+ 3.x requires maven 3.0.4+ I don't mind another 2.x release if there is a critical issue that people using maven 2.2.1 require fixed, though ideally that should be released from a 2.x branch as I wanted to move the 3.x branch to fully 3.x APIs... However as I have not cut a 3.0 yet I will not object to a 2.1 *provided* it obeys the maven 2.2.1 compatibility contract On Thursday, 6 June 2013, wrote: > ** > Revision 18374 <http://fisheye.codehaus.org/changelog/mojo/?cs=18374> > Author olamy Date 2013-06-05 21:11:14 -0500 (Wed, 05 Jun 2013) Log Message > > next version will be 2.1-SNAPSHOT > > Modified Paths > > - > trunk/mojo/versions-maven-plugin/pom.xml<#13f17426232a5cb0_trunkmojoversionsmavenpluginpomxml> > > Diff > Modified: trunk/mojo/versions-maven-plugin/pom.xml (18373 => 18374) > > --- trunk/mojo/versions-maven-plugin/pom.xml 2013-06-06 01:58:52 UTC (rev > 18373) > +++ trunk/mojo/versions-maven-plugin/pom.xml 2013-06-06 02:11:14 UTC (rev > 18374)@@ -9,7 +9,7 @@ <groupId>org.codehaus.mojo</groupId> > <artifactId>versions-maven-plugin</artifactId>- > <version>3.0-SNAPSHOT</version>+ <version>2.1-SNAPSHOT</version> > <packaging>maven-plugin</packaging> <name>Versions Maven Plugin</name> > > ------------------------------ > > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > -- Sent from my phone
