[
http://jira.codehaus.org/browse/MRELEASE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270374#comment-270374
]
David Fischer commented on MRELEASE-525:
----------------------------------------
I'm having the same problem.
To be more precise, what happens is that the update-versions goal
systematically appends "-SNAPSHOT" to the developmentVersion passed as a -D
argument.
You can verify this behavior by using -DdevelopmentVersion=1.0.0 *without* -B.
You will be prompted for a version, but the default value will be
1.0.0-SNAPSHOT (or whatever version you passed in the command line).
It seems that this goal is only meant to prepare for the next version, hence
the -SNAPSHOT. But if you use is interactively, it will accept a version number
without the trailing SNAPSHOT, which is inconsistent.
> Update-versions does not work in batch mode
> -------------------------------------------
>
> Key: MRELEASE-525
> URL: http://jira.codehaus.org/browse/MRELEASE-525
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
>
> When I run the release:update-versions goal in batch mode, it performs the
> transformation and just cleans the things up...
> Command which is executed:
> mvn -B release:update-versions -DautoVersionSubmodules=true
> -DdevelopmentVersion=0.4.0
> The output looks like:
> [INFO] Transforming 'ModuleA'...
> [INFO] Transforming 'ModuleB'...
> [INFO] Cleaning up after release...
> If I run the command in interactive mode, everything goes fine:
> mvn -B release:update-versions -DautoVersionSubmodules=true
> It asks the version on the prompt and updates the pom files accordingly.
> Any idea?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
