that used to be true with Maven 2, but is not any more since Maven 3 and its m-site-p 3.0 version
Notice that Maven 3.0.x issues a misleading warning about missing version in reporting section: see MNG-5477 with m-site-p 3.4, even configuration content from pluginManagement is injected to reporting: see MSITE-516/MSHARED-338 and little note in http://maven.apache.org/shared/maven-reporting-exec/ Regards, Hervé Le vendredi 3 octobre 2014 12:46:21 Paul Benedict a écrit : > <pluginManagement> only affects <plugins> -- it does not affect <reporting>: > https://jira.codehaus.org/browse/MNG-3385 > > Cheers, > Paul > > On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[email protected]> > > wrote: > > we using <pluginManagement> for this > > > > On 3 October 2014 07:24, Kathryn Huxtable <[email protected]> > > > > wrote: > > > I’ve always used <properties>, but would it work to use > > > <buildDependencies>? -K > > > > > > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[email protected]> wrote: > > > > I use the maven-javadoc-plugin in both <build> and <reporting>. I > > > > don't > > > > want to fall back to <properties> to share the plugin version. Is > > > > there a > > > > > > better way than using <properties>? > > > > > > > > Cheers, > > > > Paul > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > -- > > WBR > > Maxim aka solomax --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
