You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bernd Mau (JIRA)" <ji...@codehaus.org> on 2011/04/08 15:23:22 UTC
[jira] Created: (MRELEASE-674) release plugin converts explicit
version to snapshot
release plugin converts explicit version to snapshot
-----------------------------------------------------
Key: MRELEASE-674
URL: http://jira.codehaus.org/browse/MRELEASE-674
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.1
Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: i:\tools\jdk\1.6.0_23\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
Reporter: Bernd Mau
Attachments: MapVersionPhase.patch
I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion().
I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false
I made a patch and attached it to the issue.
--
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
[jira] (MRELEASE-674) release plugin converts explicit version to
snapshot
Posted by "Jim McCaskey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298493#comment-298493 ]
Jim McCaskey commented on MRELEASE-674:
---------------------------------------
I've noticed the release plugin has been released a few times with out this even though a patch is available. I was curious if there was any reason why.
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Attachments: MapVersionPhase.patch
>
>
> I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion().
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false
> I made a patch and attached it to the issue.
--
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-674) release plugin converts explicit version to
snapshot
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-674:
------------------------------------
Description:
I would like to use {{release:update-versions}} to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in {{MapVersionPhase.getNextVersion()}}.
I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
{{mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
I made a patch and attached it to the issue.
was:
I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion().
I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false
I made a patch and attached it to the issue.
Fix Version/s: 2.4
Assignee: Robert Scholte
The number of open issues is huge, it'll take some time to clean it up. I'll mark this for the 2.4 release.
You could help if you could provide an integration-test
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: MapVersionPhase.patch
>
>
> I would like to use {{release:update-versions}} to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in {{MapVersionPhase.getNextVersion()}}.
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> {{mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
> I made a patch and attached it to the issue.
--
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-674) release plugin converts explicit version to
snapshot
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reopened MRELEASE-674:
-------------------------------------
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: MapVersionPhase.patch
>
>
> I would like to use {{release:update-versions}} to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in {{MapVersionPhase.getNextVersion()}}.
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> {{mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
> I made a patch and attached it to the issue.
--
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-674) release plugin converts explicit version to
snapshot
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-674.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.4)
Marking this as {{won't fix}}, since there's another parameter which should be used.
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Assignee: Robert Scholte
> Attachments: MapVersionPhase.patch
>
>
> I would like to use {{release:update-versions}} to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in {{MapVersionPhase.getNextVersion()}}.
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> {{mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
> I made a patch and attached it to the issue.
--
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-674) release plugin converts explicit version to
snapshot
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-674.
-----------------------------------
Resolution: Fixed
Sounds to me you should use {{updateWorkingCopyVersions=false}}. MRELEASE-760 has been fixed, so this should work with the next release.
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: MapVersionPhase.patch
>
>
> I would like to use {{release:update-versions}} to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in {{MapVersionPhase.getNextVersion()}}.
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> {{mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
> I made a patch and attached it to the issue.
--
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] Commented: (MRELEASE-674) release plugin converts explicit
version to snapshot
Posted by "Jim McCaskey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277665#comment-277665 ]
Jim McCaskey commented on MRELEASE-674:
---------------------------------------
FWIW: I have verified that this patch works for the use case specified.
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Attachments: MapVersionPhase.patch
>
>
> I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion().
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false
> I made a patch and attached it to the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-674) release plugin converts explicit version to
snapshot
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-674:
------------------------------------
Component/s: (was: prepare)
update-versions
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Attachments: MapVersionPhase.patch
>
>
> I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion().
> I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line:
> mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false
> I made a patch and attached it to the issue.
--
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