Ah! I see, I'd assumed that the 'local' meant that it was using file based CVS access rather than pserver / ext etc.
Thanks for the help! - Tim -----Original Message----- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 01 June 2007 19:22 To: [EMAIL PROTECTED] Subject: Re: CVS Local checkout oh, I didn't see you use the local provider and not the cvs provider. The local provider copy files and it is independant of cvs or other scm providers. Your scm url is totally wrong for cvs: http://maven.apache.org/scm/cvs.html 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 > > >
