You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/08/02 11:43:21 UTC

[jira] (MRELEASE-783) release:update-versions should not need SCM config

    [ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305279#comment-305279 ] 

Robert Scholte commented on MRELEASE-783:
-----------------------------------------

{quote}org.apache.maven.plugins:maven-release-plugin:2.0:update-versions{quote}

Could you upgrade to version 2.3.2, because I'm pretty sure this is already fixed.
                
> release:update-versions should not need SCM config
> --------------------------------------------------
>
>                 Key: MRELEASE-783
>                 URL: https://jira.codehaus.org/browse/MRELEASE-783
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>            Reporter: Ondrej Zizka
>
> Currently, on a project without <scm> configured, {{mvn release:update-versions}} ends up with:
> {code}
> Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:update-versions (default-cli) on project wicketstuff-dojo: Missing required setting: scm connection or developerConnection must be specified.
> {code}
> Updating versions recursively definitely does not need SCM.
> Could this restriction be removed? Thanks.

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