[ http://jira.codehaus.org/browse/MNG-2339?page=comments#action_67975 ]
Carlos Sanchez commented on MNG-2339:
-------------------------------------
In surefire-providers
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>surefire-api</artifactId>
<version>2.1-SNAPSHOT</version>
<!-- commenting this due to MNG-2339
<version>${project.version}</version>
-->
</dependency>
If you put back <version>${project.version}</version>, deploy and clean your
repo org/apache/maven/surefire dir, you'll get the problem
> ${project.*} are interpreted in the wrong place
> -----------------------------------------------
>
> Key: MNG-2339
> URL: http://jira.codehaus.org/browse/MNG-2339
> Project: Maven 2
> Type: Bug
> Components: General
> Versions: 2.0.4
> Reporter: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0.5
>
>
> If a plugin use ${project.version}, this parameter is interpreted with the
> version of the current project and not the plugin version. I think we have
> the same pb with dependencies and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT,
> ${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT
> instead of 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
