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 :)
Thanks, mohan kr -----Original Message----- From: Jeff Storey [mailto:[email protected]] Sent: Thursday, July 09, 2009 9:21 AM To: [email protected] Subject: Reporting Plugins Not Inheriting Versions Hi, I have a few reporting plugins defined in the reporting section of my POM. According to http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins, when I invoke the goals from the command line, the configurations from the reporting sections should be used. The configurations are in fact used, but the versions are not. For example, I defined cobertura 2.2 in the reporting section, but when I run mvn cobertura:cobertura, it fetches the latest version (2.3) from the repository. In order to make this work, I need to list the plugin in both the reporting and plugins sections (though I only need to list the configuration in the reporting section). Is there a way to automatically pull the version from the reporting section as well? My current approach is to list it in both places and use a property for the version number. Thanks, Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
