maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Cooke (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git
Date Sun, 20 Jan 2013 21:50:13 GMT

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

Fred Cooke commented on MRELEASE-777:
-------------------------------------

I understand local clones, but the m-rel-p output in question is this:

[INFO] Executing: /bin/sh -c cd /home/fg/src/json-schema-validator/target && git clone
git@github.com:fge/json-schema-validator /home/fg/src/json-schema-validator/target/checkout

That ain't using hard links ;-) Maybe it's from an old plugin version?
                
> 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