any one? or is it just me seeing this behavior? -D
On 8/16/07, Dan Tran <[EMAIL PROTECTED]> wrote: > Hello, > I am seeing some strange behaviors in alpha, beta-1, and beta-2 ( > still instaging area), that I hope someone can explain and/or confirm. > > - Unable to sync the project source when Continuum runs under NT > service with a known admin user id. > > the build log shows > Provider message: The svn command failed. > Command output: > > ------------------------------------------------------------------------------- > 'svn' is not recognized as an internal or external command, > operable program or batch file. > > ------------------------------------------------------------------------------- > > here is log/continuum.log fragment > > 89674 [pool-1-thread-1] INFO > org.apache.maven.scm.manager.ScmManager:default - Executing: cmd.exe > /X /C '"svn --non-interactive update"' > 89674 [pool-1-thread-1] INFO > org.apache.maven.scm.manager.ScmManager:default - Working directory: > C:\dev\continuum\working-directory\1.1\1 > 89736 [pool-1-thread-1] WARN > org.apache.maven.continuum.scm.ContinuumScm:default - Error while > updating the code for project: 'Sentinel', id: '1' to > 'C:\dev\continuum\working-directory\1.1\1'. > 89736 [pool-1-thread-1] WARN > org.apache.maven.continuum.scm.ContinuumScm:default - Command output: > 'svn' is not recognized as an internal or external command, > operable program or batch file. > > > However, there is no build problem when starting Continuum from > commandline ( with the same login account) > > the SVN.exe definitely is in the SYSTEM path > > - There is no build problem when use with local SYSTEM account. The > local repo ends up at c:\.m2\repository. This is not a viable > workaround since my InstallAnywhere Installer requires a valid account > due to licensing. > > > Any suggestion is greatly appreciated. > > -D >
