[ http://jira.codehaus.org/browse/SCM-200?page=all ]
Alex Mayorga Adame closed SCM-200:
----------------------------------
Resolution: Won't Fix
This happens when a non-standard port is used and CVS is not present on the
PATH of the Continuum environment.
Make sure path to CVS/bin is somewhere in the PATH to fix this problem.
This would be superceded by a documentation improvement and a bug about the way
Continuum outputs CVS exceptions that don't make obvious the real problem
behind this error.
> Problem checking out a CVS project when a non standard port is used
> -------------------------------------------------------------------
>
> Key: SCM-200
> URL: http://jira.codehaus.org/browse/SCM-200
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-cvs
> Versions: 1.0-beta-3
> Environment: Solaris, Maven 2.0.4, Continuum 1.0.3
> Reporter: Alex Mayorga Adame
> Assignee: Alex Mayorga Adame
>
>
> I've been experiencing problems on initial checkout of a Maven 2 project
> under Continuum 1.0.3 when using following syntax of SCM:
> {{scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module}}
> Error in Continuum is as follows:
> {{Provider message: The cvs command failed.}}
> {{Command output:}}
> {{------------------------------------------------------------------------------}}
> {{port/repository: no such repository}}
> {{cvs checkout: authorization failed: server host rejected access to
> port/repository for user user}}
> {{cvs checkout: used empty password; try "cvs login" with a real password}}
> {{-------------------------------------------------------------------------------}}
> Looks like the provider is preppending the port to the repository and trying
> a wrong CVS command.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
