On Thu, Jul 14, 2011 at 1:27 AM, Jörg Schaible <[email protected]> wrote: > Moser, Christian wrote: > >>> Each plugin decides if it will allow "skip", and so the plugin still >>> needs to get loaded to decide whether to skip. >> >> This makes sense. Will add javadoc-plugin. >> >>> What do you mean by "maven super pom"? >> >> Maybe "maven super pom" was confusing sorry for that. >> I meant the "place" where maven specified, which version for the "default" >> plugins is used. For example, M3 will show a warning if you use, for >> example versions-plugin without declaring a version in the pom. But I >> guess it's possible to run a build without declaring deploy-plugin and not >> to receive a warning. So, somewhere the deploy-plugin is declared for the >> current Maven version, isn't it?
I think the default version is LATEST, which means there is no locking down of versions > But this is the whole point of locking them down: Different Maven versions > define also different plugin versions. How should your build be repeatable > then? As Jörg points out, that means your build is not repeatable. In a years time, if someone checks out your tagged source and run maven it may work, but chances are there are new features in the build that may cause gotchas. To avoid these its best practice to lock down versions of plugins in your corporate pom. I see you've already got enforcer, so over time as you run through all the lifecycles you will gradually fill in the blanks for any unspecified plugins into your corporate pom. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
