[jira] Closed: (MRELEASE-70) ${version} in dependencyManagement is replaced after release:prepare

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRELEASE-70?page=all ]
     
Brett Porter closed MRELEASE-70:
--------------------------------

     Assign To: Brett Porter
    Resolution: Fixed

> ${version} in dependencyManagement is replaced after release:prepare
> --------------------------------------------------------------------
>
>          Key: MRELEASE-70
>          URL: http://jira.codehaus.org/browse/MRELEASE-70
>      Project: Maven 2.x Release Plugin
>         Type: Bug

>  Environment: xp, 2.0.2-SNAPSHOT, last release plugin from svn
>     Reporter: Dan Tran
>     Assignee: Brett Porter
>      Fix For: 2.0-beta-4

>
>
> In my top pom, I use ${version} to refer as the same version of the pom in my dependencyMangement.  However after release:prepare,
> ${version} is replaced at the release version. and there more my dependency-maven-plugin:copy mojo, which relies heavily to dependencyMangement
> to fill in the missing version, breaks.  It nows fills in the wrong version.
> So the work around is that I need to manually change it back to ${version} after each daily release.
> here is an example of my dependencyMangement
> <dependencyManagement>
> ...
>       <dependency>
>         <groupId>com.borland.optimizeit.components</groupId>
>         <artifactId>optimizeit</artifactId>
>         <version>${version}</version>
>         <type>zip</type>
>       </dependency>
>       <dependency>
>         <groupId>com.borland.optimizeit.components</groupId>
>         <artifactId>agent-win32</artifactId>
>         <version>${version}</version>
>         <type>zip</type>
>       </dependency>
> ...
> </dependencyManagement>

-- 
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