[
https://issues.apache.org/jira/browse/SCM-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960548#comment-17960548
]
ASF GitHub Bot commented on SCM-230:
------------------------------------
jira-importer commented on issue #425:
URL: https://github.com/apache/maven-scm/issues/425#issuecomment-2964593732
**[Al
Hoang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hoanga)**
commented
If you want the test to pass now. It might be possible to override
ChangeLongCommandTckTest to perform the behavior that you want with a huge
caveat and link to the issues at hand. This should work as a workaround until
upstream decides what they want to do with this test.
While working on the Mercurial plugin I found a couple of other crappy
assumptions in the TckTest Suite which caused me some aggravation.
> mercurial plugin
> ----------------
>
> Key: SCM-230
> URL: https://issues.apache.org/jira/browse/SCM-230
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-mercurial (hg)
> Reporter: solo turn
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-rc1
>
> Attachments: maven-scm-hg.tar.gz, maven-scm-provider-hg-0.09.tbz,
> maven-scm-provider-hg-0.8.tbz, maven-scm-provider-hg-0.8.tbz,
> maven-scm-provider-hg-0.8.tbz, maven-scm-provider-hg-1.0-SNAPSHOT.tar.gz,
> maven-scm-provider-hg.diff.gz, maven-scm-provider-hg.tar.gz,
> maven-scm-provider-hg.tgz, scm-230-patch-1.svndiff, site-patch, site-patch-2
>
>
> it would be nice to have a mercurial source provider. and if not, it would be
> nice to update the documentation on http://maven.apache.org/scm/ so that
> anybody could just copy the bzr provider and make a mercurial provider out of
> it. it should be nearly the same implementation.
> mercurial is (currently) much faster than bzr and therefor really useable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
