maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anatoly Kupriyanov (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git
Date Mon, 18 Feb 2013 16:32:13 GMT

    [ https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319896#comment-319896
] 

Anatoly Kupriyanov commented on MRELEASE-777:
---------------------------------------------

I have a project which has several thousand files in it. So even hardlinks don't do the job
significantly faster. And there is no way to tell the plugin to pull changes instead of cloning
them. As I see in the source code, the release plugin v2.4 deletes the checkout directory
first (CheckoutProjectFromScm.java:199), and it means that clone will be commenced always.
The "git clean" should be used to create an clean copy to build.
                
> 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

        

Mime
View raw message