Other test failures:
ClearCase checkout:
junit.framework.ComparisonFailure: expected:<...c...> but was:<...C...>
at junit.framework.Assert.assertEquals(Assert.java:81)
at junit.framework.Assert.assertEquals(Assert.java:87)
at
org.apache.maven.scm.provider.clearcase.command.checkout.ClearCaseCheckOutCommandTest.testCreateViewCommandLine(ClearCaseCheckOutCommandTest.java:38)
(looks like a windows drive letter, can usually be gotten around by
getting the canonical path of both strings).
cvsexe: fails due to the extreme length of the path. Is the extra level
for each provider really necessary?
maven-scm-providers/maven-scm-providers-cvs/maven-scm-provider-cvsexe
could just be
maven-scm-providers/maven-scm-provider-cvs-exe
StartTeam:
org.apache.maven.scm.ScmException:
C:\home\brett\scm\maven\scm\maven-scm-providers\maven-scm-provider-starteam\target\testdir\testfile.txt
was not contained in
c:\home\brett\scm\maven\scm\maven-scm-providers\maven-scm-provider-starteam
at
org.apache.maven.scm.provider.starteam.StarteamScmProvider.getRelativePath(StarteamScmProvider.java:340)
at
org.apache.maven.scm.provider.starteam.StarteamScmProviderTest.testGoodGetRelativeFile(StarteamScmProviderTest.java:44)
(I don't have starteam installed - do I need to?)
Cheers,
- Brett
Emmanuel Venisse wrote:
> Hi,
>
> I finished all changes in maven-scm and it's ready for the release.
>
> Can you test it with your respective scm?
> I updated release plugin, changelog plugin (at mojo.codehaus.org) and
> continuum 1.0.3 with latest maven-scm artefacts, so if you can test
> Maven-scm with them, that will be great.
>
> I'll release Maven-SCM 1.0 probably at monday if all is ok.
>
> snapshot of maven-scm is deployed so you don't need to build it.
>
> Thanks.
> Emmanuel
>
