Stephen Connolly wrote: > AFAIK, > > You need to put the version in reporting if you are using it for the > site lifecycle... if you are also using the plugin the the build > lifecycle, add version to pluginManagement... > > reporting only uses the version specified in pluginManagement if you > run the build lifecycle immediately prior to running the site > lifecycle within the same invokation of maven... thus if you don't > put the version in both places > > mvn clean && mvn install && mvn site > > will return a different result from > > mvn clean install site > > as the first will use the versions specified in <reporting> when > generating the site, while the second will use the versions specified > in <pluginManagement> when generating the site (but only if you've > attached the reporting plugin to the build lifecycle) > > Confused yet?
Well, this can be topped! Actually, if you specify (different) versions both in the pluginManagement and the reporting sections, you will also get different results with mvn clean && mvn install && mvn site and mvn clean install site First command will use the version sepcified in the reporting section, second will use the version specified in the pluginDependency (if - as Stephen already pointed out - the plugin is also used during the build lifecycle). Reason for this behaviour: 1/ The reporting section does not inherit the settings from the pluginManagement. 2/ Each plugin can be loaded once only. First usage wins. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
