[ http://jira.codehaus.org/browse/SCM-230?page=comments#action_78456 ] Ryan Daum commented on SCM-230: -------------------------------
Found the source of the problem. It is in HgChangeLogCommandTckTest, and is actually a problem in the last test in the base ChangeLogCommandTckTest. Basically it checks in two revisions then tries, using date/time filtering to retrieve only the later one. This may work fine for slow network based revision control systems, but for Mercurial, the creation of the file and its checkin happens within the same second, so the log reports the same time for creation of both revisions, and nothing fits within the date filter range. In some cases, if the checkin happens of the second file happens to occur after the second value of the date increments, the test passes. I am unable to fix this, it is IMHO a defect in the base ChangeLogCommandTckTest. > 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-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.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
