[
http://jira.codehaus.org/browse/MRELEASE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237655#action_237655
]
Brett Porter commented on MRELEASE-605:
---------------------------------------
It shouldn't change the devConnection URL, but it should know to clone from the
current directory instead if the flag is false. For git, it probably always
makes sense to do this instead of wasting bandwidth cloning the repo, since it
will be a clean copy.
However, in some situations you may want the opposite - to ensure a push has
occurred before performing the release. That might need to a separate check.
> when not pushing changes to remote git repo in 2.1, the release plugin fails
> on release:perform
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-605
> URL: http://jira.codehaus.org/browse/MRELEASE-605
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: james strachan
>
> 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.
-
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
