I just tried Maven3 (3.0-beta-3) with our build and got a (to me)
surprising result. I have the following in my POM:
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.2</version>
</plugin>
:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.4</version>
</plugin>
</plugins>
</pluginManagement>
</build>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<!-- no version -->
<snip/>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<!-- no version -->
</plugin>
</plugins>
</reporting>
The Enforcer plugin is happy with this setup but Maven 3 complains
about missing version numbers for the reporting section
(maven-project-info-reports-plugin and cobertura-maven-plugin). Isn't
the Plugin Management supposed to set the version numbers?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]