[
https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317643#comment-317643
]
Fred Cooke commented on MRELEASE-777:
-------------------------------------
Hi Mark! I saw those options, however IMO the clone concept is completely and
utterly broken. You already have the repo with a checkout, and the POM from
that, in order to even think about doing a release. You also already have the
entire history already already, because we're talking Git, not dinosaur stuff
;-) so if you want to do a clone at all, which is brain dead, even locally,
then you'd do it from the existing repo. If you don't want to do a clone, and I
assure you, you definitely do not ever want to do that, then you simply set
GIT_DIR and GIT_WORK_TREE and do a checkout of a hash. Simple as that. Long
time no see, too :-)
> release plugin shouldn't git clone if the SCM is git
> ----------------------------------------------------
>
> Key: MRELEASE-777
> URL: https://jira.codehaus.org/browse/MRELEASE-777
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Environment: Linux x86_64, maven 2.2.1
> Reporter: Joel Orlina
> Assignee: Mark Struberg
>
> See here for original issue:
> https://issues.sonatype.org/browse/MVNCENTRAL-202
--
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
