[ http://jira.codehaus.org/browse/SCM-230?page=comments#action_76723 ] Alain Hoang commented on SCM-230: ---------------------------------
I've been hacking on the 'experimental' tarball for a week or so now. I've been able to get more tests to pass however there are actually some semantic differences between bzr and mercurial that make this not as simple as find and replace on the class names to get running. Just fixing 'inventory' won't fix all of the problems. (I already did with locate) In terms of functionality, I think it works mostly but the unit tests are failing due to different semantics between mercurial and bzr. Noteably: 1. Mercurial's understanding of URLs is not the same as bzr's. For example you don't specify file:/// to reference repositories on the local filesystem. 2. The diff format is closer to subversion's diff format than the one that bzr spits out. 3. The log format is not the same I've been trying to get these to pass the unit tests but it requires rewriting quite a few of the unit tests so that it passes mercurial's notions of the tests. I'll try to post an updated tarball as soon as I can. > mercurial plugin > ---------------- > > Key: SCM-230 > URL: http://jira.codehaus.org/browse/SCM-230 > Project: Maven SCM > Issue Type: New Feature > Reporter: solo turn > Attachments: maven-scm-provider-hg.diff.gz, maven-scm-provider-hg.tgz > > > 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 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
