[ 
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marius Dumitru Florea closed MRELEASE-666.
------------------------------------------

    Resolution: Not A Bug

This issue was caused by a mistake in one of our poms: we were using 
${commons.version} instead of ${project.version} for an internal dependency 
(i.e. a jar that was generated by one of the child modules). Sorry for the 
noise.

> release:prepare can fail during rewrite-poms-for-development phase if a 
> property matches the version being released
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-666
>                 URL: http://jira.codehaus.org/browse/MRELEASE-666
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>         Environment: Linux
>            Reporter: Marius Dumitru Florea
>         Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in 
> order to create 
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
>  fails with the attached log (I attached only the final part of the console 
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if 
> release version is {{3.0-test-3}}. In other words release:prepare fails if 
> the version being released matches the {{commons.version}} property defined 
> in the parent pom. Note that after release:prepare fails all poms are ready 
> to be committed, i.e. I just had to commit them to finish the release:prepare 
> , so it looks like release:prepare manages to rewrite the poms for next 
> development iteration but fails just before committing them for some obscure 
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.

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

        

Reply via email to