2008/10/7 Edelson, Justin <[EMAIL PROTECTED]>:
> 1) A few reasons. I like having the properties all together vs. spread out
> in each pluginManagement sub-element. Easier for descendents to override the
> plugin version (for example - I'm testing a patched version of the javadoc
> plugin. This is just a matter of specifying the patched version # in the
> descendent pom). Also ensures that, for example, the same surefire version
> is used in pluginMangement and reporting.

Beware!

That will only work if you invoke the project outside of a reactor build.

Inside a reactor build, the first project to use the plugin determines
the version used by _all_ projects in the reactor.

Hope you're aware of that gotcha / bug with maven

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to