[
https://issues.apache.org/jira/browse/SCM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963271#comment-17963271
]
ASF GitHub Bot commented on SCM-799:
------------------------------------
jira-importer closed issue #1024: [SCM-799] Implement export command
URL: https://github.com/apache/maven-scm/issues/1024
> Implement export command
> ------------------------
>
> Key: SCM-799
> URL: https://issues.apache.org/jira/browse/SCM-799
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Reporter: phansson
> Priority: Major
>
> 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
(v8.20.10#820010)
