[
http://jira.codehaus.org/browse/SCM-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed SCM-571.
-----------------------------
Resolution: Not A Bug
Hi!
The original issue has already been fixed in the
maven-release-manager/maven-release-plugin. Please see MRELEASE-501. You can
activate this feature by using
$> mvn release:perform -DlocalCheckout=true
The reason why we don't call a git-checkout but git-clone instead is because we
a) need to test if the build is reproducible and b) git-checkout always works
on the repo itself, but we need to get our sources into target/checkout.
@Gunnar Gustavsson if your problem is still valid with the latest
scm-provider-gitexe, then please file a separate issue - txs!
> use checkout, not clone under release:perform
> ---------------------------------------------
>
> Key: SCM-571
> URL: http://jira.codehaus.org/browse/SCM-571
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-git
> Affects Versions: 1.4
> Reporter: John J. Franey
> Assignee: Mark Struberg
>
> In the log of a release:perform, I noticed that the git clone command is
> being run. This will be a real killer for large repositories on the other
> side of a slow network or disk drive. It can also eat up disk space. A
> checkout would be preferred. Perhaps, the following would be better:
> mkdir -p target/checkout; cd target/checkout; GIT_DIR=../../.git git checkout
> *; cd ../..
> or,
> git checkout <new tag> #do perform in the original workspace
> Regards.
--
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
