You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tom Snee (JIRA)" <ji...@codehaus.org> on 2013/02/22 20:15:13 UTC

[jira] (MRELEASE-825) updateWorkingCopyVersions=false does not change tagged POMs to release version

Tom Snee created MRELEASE-825:
---------------------------------

             Summary: updateWorkingCopyVersions=false does not change tagged POMs to release version
                 Key: MRELEASE-825
                 URL: https://jira.codehaus.org/browse/MRELEASE-825
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
          Components: prepare
    Affects Versions: 2.3
            Reporter: Tom Snee
            Assignee: Robert Scholte
             Fix For: 2.3.2


The flag updateWorkingCopyVersions (more specifically with value "false") is not handled correctly. 

Attached project is a simple Maven project with version 1.0-SNAPSHOT, depending on version 2.3 of the release plugin. It is configured with dryRun=true and updateWorkingCopyVersions=false.

When running mvn:prepare (and accepting the versions that are proposed), you'll see that pom.xml.next file contains 1.1-SNAPSHOT (the next development version) instead of 1.0 (the tagged version).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MRELEASE-825) updateWorkingCopyVersions=false does not change tagged POMs to release version

Posted by "Tom Snee (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRELEASE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Snee closed MRELEASE-825.
-----------------------------

       Resolution: Incomplete
    Fix Version/s:     (was: 2.3.2)

Sorry, I tried to save myself some typing by cloning an old issue. I will open a new issue from scratch.
                
> updateWorkingCopyVersions=false does not change tagged POMs to release version
> ------------------------------------------------------------------------------
>
>                 Key: MRELEASE-825
>                 URL: https://jira.codehaus.org/browse/MRELEASE-825
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.3
>            Reporter: Tom Snee
>            Assignee: Robert Scholte
>
> The flag updateWorkingCopyVersions (more specifically with value "false") is not handled correctly. 
> Attached project is a simple Maven project with version 1.0-SNAPSHOT, depending on version 2.3 of the release plugin. It is configured with dryRun=true and updateWorkingCopyVersions=false.
> When running mvn:prepare (and accepting the versions that are proposed), you'll see that pom.xml.next file contains 1.1-SNAPSHOT (the next development version) instead of 1.0 (the tagged version).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira