Hi,
I ran builds on a Linux box as well and observed that:
a) tests for scm provider starteam fail when run from scm project's root
directory
b) running tests from individual provider's directory run fine (including
starteam).
c) I did find that my win xp installation had TortoiseCVS client installed
which uses CVSNT binary. However, removing CVSNT and putting cvs.exe on path
didn't fix the problem with the CVScheckoutCommand test (strange that this
works on Linux!)
Also, SVN tests ran fine on windows after the svn update - thanks !
Will try if I can dig into this further...
cheers,
Rahul
----- Original Message -----
From: "Brett Porter" <[EMAIL PROTECTED]>
To: <scm-dev@maven.apache.org>
Sent: Sunday, June 26, 2005 11:06 AM
Subject: Re: scm plugin(build test failures with m2
I've seen all these before, but I can't remember how I got them. For the
number of files, I thought I fixed a bug - it was uncommitted. I'm putting
it in now - svn updated your code.
For the bytes difference - this was experienced by someone using CVSNT on
windows (it works with Cygwin). We'd really appreciate it if you can
determine the problem :) There is an open JIRA for it.
- Brett
Rahul wrote:
Hi Emmanuel,
I tried building each of the providers individually, and here's what I
get:
For CVS provider:
- CvsCheckoutCommandTest still fails with the attached error.
For SVN provider:
- SvnCheckOutCommandTckTest fails with attached error.
- SvnUpdateCommandTckTest fails with attached error.
There were quite a few errors the last time I ran "m2 install" from the
root directory for all maven-scm projects but narrowed down to above
three
errors when I ran them individually from each project's directory.
Thanks,
Rahul
