[
http://jira.codehaus.org/browse/SCM-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176765#action_176765
]
Mark Struberg commented on SCM-472:
-----------------------------------
Hah sorry my fault!
I added the SvnExeChangeLogCommandTckTest locally to check if my
maven-scm-providers-jgit JgitChangeLog is broken or if the TCK itself is not
good enough.
Will fill a separate Jira for this issue! mea culpa.
> some SVN TCK tests are broken
> -----------------------------
>
> Key: SCM-472
> URL: http://jira.codehaus.org/browse/SCM-472
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.2
> Environment: SVN 1.5.4 (r33841), Fedora 10
> 2.6.27.21-170.2.56.fc10.x86_64
> Reporter: Mark Struberg
> Fix For: 1.3
>
> Attachments:
> org.apache.maven.scm.provider.svn.svnexe.command.branch.SvnExeBranchCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.changelog.SvnExeChangeLogCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest.txt
>
>
> The following TCK tests have errors:
> *
> testCheckOutCommandTest(org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest)
> *
> testChangeLogCommand(org.apache.maven.scm.provider.svn.svnexe.command.changelog.SvnExeChangeLogCommandTckTest)
> surefire logs attached
--
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
