Hmm. I guess the mailing list doesn't like embedded links... I was referring to http://maven.apache.org/pom.html - the section referring to the pluginmanagement tag.
That's a useful distinction, but I don't think that's what the documentation says. It says, "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 POM and all inheriting POMs that add the maven-jar-plugin to the build will get the pre-process-classes execution as well." On Apr 10, 2012, at 11:50 AM, Wayne Fay wrote: >> The current POM documentation says of the pluginManagement tag that it >> will apply to the inheriting poms in a way that simply using the plugins tag >> will not. Is this the current functionality? Plan for something new? I've >> been >> using the plugins tag in my parent pom and the child poms have been >> inheriting from it just fine > > What specific line/document are you referring to? > > The obvious difference is that pluginManagement merely specifies > configuration for a plugin but does not actually bind the plugin to > the build of the parent/children, while specifying a plugin in a > parent *does* bind the plugin to the children as well. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
