Continuum use the cvs command line, so if it work from the command line, it should be the same result with continuum
Lee, Tim a écrit :
The normal checkout is fine, I use it all the time, just trying to get Continuum up and running today. Thanks, Tim -----Original Message----- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 01 June 2007 15:26 To: [email protected] Subject: Re: CVS Local checkout It isn't normal, and I'm sure you'll get the same result if you run a checkout manually. Something should be wrong in your cvs. Emmanuel Lee, Tim a écrit :Hi, I'm using an Scm Url of : scm:local:<cvs-path>:<module> - when I run the build I get the following output: 609392 [SocketListener0-1] INFO org.apache.maven.continuum.Continuum - Enqueuing 'test' (Build definition id=1). 610460 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Checking out project: 'test', id: '1' to '<path>/continuum/../continuum_writable/apps/continuum/working-directory/1'. 610557 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Checking out '<cvs-path>/<module>' to '<path>/continuum/../continuum_writable/apps/continuum/working-directory/1'. 635518 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Checked out 754 files. Note : Path & module names changed to protect the innocent :) When I look at the working-directory/1 folder I see the CVS repository files ("build.xml,v" for example) rather than the checked-out version I would normally expect "build.xml". Is this normal behaviour? Because the shell script I'm attempting to invoke is failing. Thanks! Tim
