[
https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317644#comment-317644
]
Mark Struberg commented on MRELEASE-777:
----------------------------------------
being a GIT user/contributor since 2006 I can tell you that GIT is smart enough
to _not_ copy files over. Instead GIT automatically does only reference the
local origin repo without copying any files. So this really is the best option,
because this is the only one which is really portable.
please check the -l option man git-clone
We explicitely don't use git-clone -s as we cannot guarantee that a user
doesn't do any weirdo stuff in the cloned repo which would break upstream...
Also consider that the maven-release-manager simply does a 'scm checkout' on
all SCMs. Thus in order to remain portable we just provided the local file://
URL which is known to work with all distributed SCMs without having to do some
special hacks.
A local git-clone of a 4GB git repo takes way sub-second... I really see no
reason to further improve this.
PS: being busy with a big refactoring in Apache OpenWebBeans atm, hope to be
back working on the incremental and SCM stuff in about 2 weeks.
> 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
