The answer is already given: You need file access to your continuum application. (Through ssh or on the machine itself for example) Continuum uses a work directory where the checkouts are made. Here lies the problem. (For every build the working copy is updated, not recreated.)
You need to get the subversion update properly, by executing svn update in the working copy. This will fail and you need to find out why. Probably because some files are changed locally and needs merging or removing. Hth, Nick Stolwijk -----Original Message----- From: Glauber Stéfano Rezende [mailto:[EMAIL PROTECTED] Sent: Tue 3/4/2008 17:42 To: continuum-users@maven.apache.org Subject: Re: Problem with continuum Emmanuel Venisse wrote: > On Tue, Mar 4, 2008 at 4:12 PM, Tomislav Stojcevich <[EMAIL PROTECTED]> > wrote: > > >> Isn't that what the Build Fresh option on the build definition is for? >> > > > Yes and no :) > The build fresh run a clean checkout instead of an update but it will be use > on all runs except if you change back the value. > > With a "remove working copy" button, you'll clean it without to modify your > build definitions > > > >> Doesn't it delete the working directory and re-checkout from scm? >> >> > > continue with the problem.... -- Glauber Stéfano Rezende HST Sistemas & Tecnologia CM - Configuration Manager Fone: +55 19 3294-0331 http://www.hst.com.br
