You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ondrej Zizka (JIRA)" <ji...@codehaus.org> on 2012/07/22 03:02:21 UTC
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Ondrej Zizka created MRELEASE-783:
-------------------------------------
Summary: 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Michal Kroliczek (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307367#comment-307367 ]
Michal Kroliczek commented on MRELEASE-783:
-------------------------------------------
I use 2.3.2 i got the same exception
> 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304260#comment-304260 ]
Brett Porter commented on MRELEASE-783:
---------------------------------------
Perhaps the versions-maven-plugin would be more suitable for this scenario?
> 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Ondrej Zizka (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304261#comment-304261 ]
Ondrej Zizka commented on MRELEASE-783:
---------------------------------------
Probably, thanks for the tip; but still :)
> 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-783:
------------------------------------
Component/s: update-versions
> 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
> Components: update-versions
> 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-783.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in [r1411360|http://svn.apache.org/viewvc?rev=1411360&view=rev]
> 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
> Components: update-versions
> Reporter: Ondrej Zizka
> Assignee: Robert Scholte
> Fix For: 2.4
>
>
> 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
[jira] (MRELEASE-783) release:update-versions should not need SCM
config
Posted by "Ondrej Zizka (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304259#comment-304259 ]
Ondrej Zizka commented on MRELEASE-783:
---------------------------------------
Maven 3.0.4
> 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