I am not able to find any indication of this fix in release notes under 3.x
But I do recall Hervé did some work on it -D On Fri, Oct 3, 2014 at 12:01 PM, Manfred Moser <[email protected]> wrote: > This has been fixed and should work. But properties might still be the > better approach.. > > Paul Benedict wrote on 03.10.2014 10:46: > > > <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] > >
