I already explained this. If the version is not defined/locked through pluginManagement, Maven selects the latest version (by looking in the maven-metadata.xml file in the repos, so if the metadat is incorrect, it might not get the actual latest version). The pluginManagement section could either be in your project (pom), in a parent pom, or in the super-POM. Use help:effective-pom to see the effective pom in use. But, as I said, I've already explained this for you.
/Anders On Wed, Jul 7, 2010 at 19:45, asookazian <[email protected]> wrote: > > well, I answered one of my questions: > > mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-5:generate > > which worked. > > So I'm using mvn 2.0.8, but I believe the algorithm it uses to select the > plugin version (when not explicitly specified) may be the same with 3.0... > -- > View this message in context: > http://maven.40175.n5.nabble.com/which-version-of-a-plugin-will-Maven-use-tp1044797p1044799.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] > >
