[
http://jira.codehaus.org/browse/MRELEASE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210986#action_210986
]
Brett Porter commented on MRELEASE-525:
---------------------------------------
sounds like a bug on two levels:
a) that it doesn't work when the dev't version is set on the cmd line
b) that it prompts for anything when -B is set (it should use a default)
I haven't tried to confirm the behaviour yet though.
Was this something that worked for you in previous versions of the release
plugin?
> 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.
-
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
