The big difference in the cvs client between 1.0.3 and 1.1 is that 1.1 use a
pure java cvs client instead of the command line.
Do you reuse the working copy from your 1.0.3 to 1.1? I don't know if the
netbeans cvs client store date under CVS directory in the same way that the
command line cvs client.
If you can't use the embedded cvs client, you can use the command line one, in
your wrapper.conf, you can add this line:
wrapper.java.additional.9=-Dmaven.scm.provider.cvs.implementation=cvs_native
near the line 41
Emmanuel
Rodrigo Gonçalves a écrit :
Hi...
My problem is a little peculiar.
I have Continuum running as a service. I also have Pageant (PuTTY
authentication agent) running as a service in order to allow Continuum
to checkout the projects from CVS without any problems.
Everything works fine, until I do the upgrade form 1.0.3 to 1.1 alpha2.
I add a project with many modules, and some of them don't work. The
error given by Continuum is the following:
"Provider message: The cvs command failed."
There is no error with the SCM info and all the other modules and
projects are working fine, thats the strange thing.
In the Continuum's wraper.log:
"
INFO Continuum:default - Enqueuing 'WOW' (Build definition
id=21).
INFO BuildController:default - Initializing build
INFO BuildController:default - Starting build of RNDapp
INFO BuildController:default - Updating working dir
INFO BuildController:default - Performing action
check-working-directory
INFO BuildController:default - Performing action
update-working-directory-from-scm
INFO ContinuumScm:default - Updating project: id: '1', name
'RNDapp'.
INFO ScmManager:default - Executing: cvs -z3 -f -q update -d
INFO ScmManager:default - Working directory:
C:\Programs\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1
Warning: The server is not supporting gzip-file-contents request, no
compression is used.
org.netbeans.lib.cvsclient.response.ResponseFactory$IllegalArgumentException2:
<html>Received unknown response from
server:<p><tt>a-data>description</meta-data></tt><p>Check your setup
please:<ul><li>Are you connecting to supported CVS server?<li>Is not
misconfigured <tt>CVS_SERVER</tt> environment variable?<li>For
<tt>:local:</tt> repositories:<br>What <tt>cvs</tt> binary is
executed?<br>It is defined by <tt>CVS_EXE</tt> environment variable.</ul>
at
org.netbeans.lib.cvsclient.response.ResponseFactory.createResponse(ResponseFactory.java:70)
at org.netbeans.lib.cvsclient.Client.handleResponse(Client.java:568)
at org.netbeans.lib.cvsclient.Client.processRequests(Client.java:520)
at
org.netbeans.lib.cvsclient.command.update.UpdateCommand.execute(UpdateCommand.java:286)
at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:629)
at
org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.executeCommand(CvsConnection.java:94)
at
org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:478)
at
org.apache.maven.scm.provider.cvslib.cvsjava.command.update.CvsJavaUpdateCommand.executeCvsCommand(CvsJavaUpdateCommand.java:52)
at
org.apache.maven.scm.provider.cvslib.command.update.AbstractCvsUpdateCommand.executeUpdateCommand(AbstractCvsUpdateCommand.java:60)
at
org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:62)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
at
org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:521)
at
org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(AbstractCvsScmProvider.java:659)
at
org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:931)
at
org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:906)
at
org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:878)
at
org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:245)
at
org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:75)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:406)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.updateWorkingDirectory(DefaultBuildController.java:378)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:112)
at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
WARN ContinuumScm:default - Error while updating the code for
project: 'RNDapp', id: '1' to
'C:\Programs\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1'.
WARN ContinuumScm:default - Command output:
WARN ContinuumScm:default - Provider message: The cvs command
failed.
INFO BuildController:default - Merging SCM results
INFO BuildController:default - Error updating from SCM, not
building
"
But when I execute the command 'cvs -z3 -f -q update -d' inside the
given directory there is no problem at all.
Any ideas, tips, subjections, references, anything....
Would be very appreciated!
Regards,
Rodrigo.
