> 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 maintance a corporate pom and wonder why this error message only appear while 
using the maven-release-plugin:2.1:perform

Chris

-----Ursprüngliche Nachricht-----
Von: Barrie Treloar [mailto:[email protected]] 
Gesendet: Mittwoch, 13. Juli 2011 14:32
An: Maven Users List
Betreff: Re: Locking down default plugin versions

On Wed, Jul 13, 2011 at 8:59 PM, Moser, Christian <[email protected]> wrote:
> I'm skipping javadoc, do you know  why javadoc-plugin is needed?

Skipping a plugin isn't a built-in maven feature.
Each plugin decides if it will allow "skip", and so the plugin still
needs to get loaded to decide whether to skip.
So its still a good practice to lock down the version.

> Furthermore, I wonder if it's even a good idea to lock down
> maven-deploy-plugin because it's already specified in maven super pom.

What do you mean by "maven super pom"?
Since maven is telling you its not locked down I suspect that you
aren't using the maven super pom.
Which leads me to the next question, why would you want to?
Unless you are an apache project using the maven super pom is probably
not what you want.
You want to define these things in a corporate super pom instead.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to