[
https://issues.apache.org/jira/browse/SCM-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962120#comment-17962120
]
ASF GitHub Bot commented on SCM-571:
------------------------------------
jira-importer commented on issue #789:
URL: https://github.com/apache/maven-scm/issues/789#issuecomment-2964624230
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
Hi!
The original issue has already been fixed in the
maven-release-manager/maven-release-plugin. Please see
MRELEA[SE-501](https://issues.apache.org/jira/browse/SE-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: https://issues.apache.org/jira/browse/SCM-571
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.4
> Reporter: Gerald Jerome
> Assignee: Mark Struberg
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
