It seems your central files are very out of date, as you can see here: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml Do you have a proxy or repository manager caching it?
This still seems unusual, since from Maven 2.0.9 onwards the version of the surefire plugin was fixed to 2.4.2 unless overridden. Maybe it is a bug in the help plugin. When you run the actual tests, use -X and see what version of surefire actually gets used. This should help pinpoint what is going wrong. Cheers, Brett 2008/8/27 Rintcius <[EMAIL PROTECTED]> > > In both the the parent and child pom, there's no version 2.2. The only > version that is mentioned is 2.4.3. > However, I took a look in the repository and that gave some info. > Here's the output that I think is relevant: > > > ls > 2.2 > 2.3 > 2.4.2 > 2.4.3 > maven-metadata-apache.incubating.releases.xml > maven-metadata-apache.m2.repo.xml > maven-metadata-apache.m2.repo.xml.sha1 > maven-metadata-central.xml > maven-metadata-central.xml.sha1 > maven-metadata-codehaus.repo.xml > maven-metadata-hello2morrow repository.xml > maven-metadata-java.net2.xml > maven-metadata-maven.liftweb.net.xml > maven-metadata-maven2-repository.dev.java.net.xml > maven-metadata-maven2.iodp.usio.xml > maven-metadata-open.iona.m2-all.xml > maven-metadata-open.iona.m2-all.xml.sha1 > maven-metadata-open.iona.m2.xml > maven-metadata-scala-tools.org.xml > maven-metadata-tlc.xml > > > cat maven-metadata-apache.m2.repo.xml > > <?xml version="1.0" encoding="UTF-8"?><metadata> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-surefire-plugin</artifactId> > <version>2.1.3</version> > <versioning> > <latest>2.4.2</latest> > <release>2.4.2</release> > <versions> > <version>2.0-beta-1</version> > <version>2.0</version> > <version>2.1</version> > <version>2.1.1</version> > <version>2.1.2</version> > <version>2.1.3</version> > <version>2.2</version> > <version>2.3</version> > <version>2.3.1</version> > <version>2.4</version> > <version>2.4.1</version> > <version>2.4.2</version> > </versions> > <lastUpdated>20080215231214</lastUpdated> > </versioning> > </metadata> > > > cat maven-metadata-central.xml > > <?xml version="1.0" encoding="UTF-8"?><metadata> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-surefire-plugin</artifactId> > <version>2.1.3</version> > <versioning> > <latest>2.2</latest> > <release>2.2</release> > <versions> > <version>2.0-beta-1</version> > <version>2.0</version> > <version>2.1</version> > <version>2.1.1</version> > <version>2.1.2</version> > <version>2.1.3</version> > <version>2.2</version> > </versions> > <lastUpdated>20060514041238</lastUpdated> > </versioning> > </metadata> > > The contents of "cat maven-metadata-central.xml" seems to be the reason > why > help:describe returns 2.2. At least I can change the output of > help:describe > to 2.4.3 by changing all 2.2. occurrences in this file to 2.4.3 (and I also > changed the lastUpdated, not sure whether that is actually needed). > > But I still cannot find a reason why "help:describe" would return something > different than "help:effective-pom". > > And while I have some intuition what is going on in the repository, I don't > understand its exact mechanics. > E.g. there is a plugin version 2.4.3 (see ls output above) but none of the > metadata files contains a 2.4.3 version. I would guess that downloading a > new version of the plugin would also give rise to one of the metadata > entries being updated. > > - Rintcius > -- > View this message in context: > http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--tp19168212p19177314.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
