[
https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319897#comment-319897
]
Fred Cooke commented on MRELEASE-777:
-------------------------------------
My solution to this using variables wouldn't help you, however is likely
correct from a historical point of view for most and would be a fraction faster
than the hard-link clone. The trouble with your repo is that the hard links
apply to the git objects, not the checked out tree, so merely creating a second
copy is not acceptable for you, no matter how it's done. I've never understood
why it's deemed necessary to create a second copy anyway. The system already
checks to ensure that the original copy is clean before proceeding, why not
just use it? +1 for an option to not do anything at all and just build in place.
> 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
