1) the super-POM still applies. 2) Right. There is one for each repo. Maven will merge these, but also check the remote repos. Don't bother with this, I just mentioned it as there could be cases where Maven isn't pulling the latest due to incorrect meta data.
/Anders On Wed, Jul 7, 2010 at 21:57, asookazian <[email protected]> wrote: > > > Anders Hammar wrote: > > > > 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 > > > > > > 1) It's possible to exec 'mvn archetype:generate' in a directory that does > not have a pom.xml in it (I just did this). In this case, the > pluginManagement, etc. is irrelevant (why should you need a POM to create a > new project based on a template?) > > 2) There are many maven-metadata*.xml files in > .m2\repo2\org\apache\maven\plugins\maven-archetype-plugin directory. Which > one does Maven use? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/which-version-of-a-plugin-will-Maven-use-tp1044797p1044824.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] > >
