[
https://jira.codehaus.org/browse/MRELEASE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274346#comment-274346
]
james strachan commented on MRELEASE-605:
-----------------------------------------
Just wanted to say a big thank you! Works like a charm. Its made one geek very
happy :). Just did a release without having to muck about with connectionUrl -
yay!
> when not pushing changes to remote git repo in 2.1, the release plugin fails
> on release:perform
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-605
> URL: https://jira.codehaus.org/browse/MRELEASE-605
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: james strachan
> Assignee: Mark Struberg
> Fix For: 2.2
>
>
> as it tries to clone the remote repo, which has not yet been pushed - so
> there's no tag in the remote repo yet.
> Ideally if pushChanges is false, it should use a value of
> {code}
> <scm>
> <developerConnectionL>scm:git:file://${baseDir}</developerConnection>
> ...
> </scm>
> {code}
> so that it clones from the current local git repo (which has everything
> inside it) rather than the remote repo which has yet to be pushed.
> BTW a great use case for not pushing is using a staging maven repo like
> Nexus; which may reject an attempt to promote a staged build, so you only
> want to push after a downstream stage works.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
