So there is an error in the official maven documentation at
http://maven.apache.org/pom.html#Plugin_Management, quoting
> *If we added these specifications to the plugins element, they would apply
> only to a single POM.*
> However, if we apply them under the pluginManagement element, then this
Maven 2 to Maven 3.
Thanks.
--- On Sun, 1/16/11, Wayne Fay wrote:
From: Wayne Fay
Subject: Re: use of plugin and pluginmanagement
To: "Maven Users List"
Date: Sunday, January 16, 2011, 8:27 PM
> Maven documentation authors - please study Wayne's concise statement below.
> Maven documentation authors - please study Wayne's concise statement below.
> That is
> what we need in the Maven documentation. Not the long-winded,
> stream-of-consciousness
> that the existing maven docs currently are.
Thanks Dean. I was just recently invited to join Maven dev team and I
. Not the long-winded,
stream-of-consciousness that the existing maven docs currently are.
--- On Fri, 1/14/11, Wayne Fay wrote:
From: Wayne Fay
Subject: Re: use of plugin and pluginmanagement
To: "Maven Users List"
Date: Friday, January 14, 2011, 9:05 AM
> What extra things p
thanks,
> What extra things provides than using only .
PluginManagement does ONE THING ONLY (essentially).
It provides a central location for all of your plugin versioning and
configuration.
THAT'S IT.
You still need to declare the in the section of your
various poms (children or parents) where you ac
Hi All,
Are the and behave in same way as
far as inheritance of and are concerned
respectively...
Because I found two contrast behavior from these two :
1. In case of all plugins specified in Parent POM get
inherited by child POM.
-> Example: SUPER POM has a default set of plugins defi
