[
https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317637#comment-317637
]
Fred Cooke commented on MRELEASE-777:
-------------------------------------
Guys, I see this is closed, however even if those options fix this guy's
situation, doing a git clone is absolutely not an acceptable thing to do under
any circumstances, is NOT analogous to an SVN checkout, and is for sure a "bug"
or at least poor implementation. The *entire* repo is already local. The only
sane things to do might be fetch or pull to ensure you're up to date, and do a
checkout with GIT_DIR and GIT_WORK_TREE variables set appropriately. Can we
reopen this until that's resolved? I had no idea that it was doing this during
my releases, and am slightly disturbed to have read this. I only stumbled
across it having a chat to the reporter in the freenode channel about some
enhancements that he and I would both love to see, but that's another topic for
some other issues :-)
> 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
