Specifying <version> for a plugin in <pluginManagement> does not force Maven to
use this version
------------------------------------------------------------------------------------------------
Key: MNG-1424
URL: http://jira.codehaus.org/browse/MNG-1424
Project: Maven 2
Type: Bug
Components: maven-core
Versions: 2.0
Environment: Win2k, M2.0, Java 1.4.2
Reporter: Fabrice BELLINGARD
Priority: Critical
Fix For: 2.0.1
I had the problem when I wanted to use the final release of the surefire
plugin. I put the following in my root POM:
<build>
...
<pluginManagement>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.0</version>
</plugin>
</plugins>
</pluginManagement>
</build>
, but Maven still used version 2.0-beta-4 (and therefore did not try to
download version 2.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
