Stephen Connolly wrote at Freitag, 10. Juli 2009 09:59: > 2009/7/10 Jörg Schaible <[email protected]> > >> Mohan KR wrote at Donnerstag, 9. Juli 2009 20:06: >> >> > Yup..got bitten by it..As a "best practice" you have to lock down the >> > plugin version >> > in the reporting section, it is *not* propogated from the >> pluginManagement >> > I believe. >> > (at least not in 2.0.9), I believe there is a JIRA issue to have a >> > reportingManagement >> > section or supposed to be fixed in 3.0.x :) >> >> Additionally you have to keep in mind, that a plugin is only loaded once >> in the reactor i.e. if a plugin is used during build as well as for the >> reports (like surefire) the version of the plugin used during the >> build "wins" and the version defined in the report section is ignored >> completely (just like both version are ignored in a reactor build if the >> plugin has been used before in another project of the build). >> > > That is only true if you invoke the build lifecycle first... > > mvn site install > > vs > > mvn install site > > ;-)
Apart from the fact that then the version configured in the pluginMgmt is ignored ... >:-) - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
