[ 
http://jira.codehaus.org/browse/MRELEASE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266334#action_266334
 ] 

Per RovegÄrd commented on MRELEASE-501:
---------------------------------------

I want to do a local checkout, but git clone fails since ${basedir} isn't the 
root of my git repository. The git root is one level up, so ${basedir}/..

How do I tell the plugin where my git root is?

> create the possibility for performing a local checkout instead a clean 
> checkout from the upstream repository for DSCMs
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-501
>                 URL: http://jira.codehaus.org/browse/MRELEASE-501
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: perform
>    Affects Versions: 2.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 2.0
>
>
> For distributed SCMs like GIT, JGit, hg, etc we don't need to do a e.g. 
> git-clone git://upstreamserver.com/location but should only do a 
> localCheckout. This would be possible by simply cloning from 
> file://${basedir} in the release:perform phase if -DlocalCheckout=true is 
> used.
> This option will speed up the builds of large projects heavily since no 
> network transfer is needed. Usually DSCMs also have the feature to only 
> create hardlinks instead of copying all files in the repo. I know this works 
> really well for GIT [1] but have to check this feature with JGit. In any case 
> omitting the network transfer would be a huge blast on it's own.
> [1] http://www.kernel.org/pub/software/scm/git/docs/git-clone.html  (--local)

-- 
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


Reply via email to