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?
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? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
