You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Hansson (JIRA)" <ji...@apache.org> on 2015/06/23 13:48:00 UTC
[jira] [Comment Edited] (SCM-799) Implement export command
[ https://issues.apache.org/jira/browse/SCM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597521#comment-14597521 ]
Peter Hansson edited comment on SCM-799 at 6/23/15 11:47 AM:
-------------------------------------------------------------
Oh boy. Was I wrong. There's a good reason this doesn't exist:
The {{hg archive}} command does not work on remote repos !
Closing this request.
was (Author: phansson):
Oh boy. Was I wrong. There's a good reason this doesn't exist:
The [[hg archive}} command does not work on remote repos !
Closing this request.
> Implement export command
> ------------------------
>
> Key: SCM-799
> URL: https://issues.apache.org/jira/browse/SCM-799
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Reporter: Peter Hansson
>
> Currently the hg provider does not implement the {{export}} command.
> Recap: The {{export}} command terminology originates from the SVN world. It means to get the sources without the SCM stuff, just sources, nothing else.
> The equivalent in Mercurial world is {{hg archive}}. It was first implemented in 2006 (in version 0.9).
> I don't see a reason why the hg provider would _not_ support the {{export}} command. Sometimes the source is really all you want. Doing an actual {{checkout}} (aka {{hg clone}}) can take a lot more time than {{export}} (aka {{hg archive}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)