continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-481) Continuum ignores .cvspass
Date Wed, 30 Nov 2005 16:31:06 GMT
    [ ] 

Emmanuel Venisse commented on CONTINUUM-481:

cvs -f -q update -d isn't a wrong command.
-d is an option of update command for retrieving absent directories (

your command and command run by continuum are the same, the only difference is that you don't
run it in the same directory

tortoiseCvs doens't use a standard cvs client but cvsNT that doesn't use .cvspass file. CvsNT
store password in windows registry, it's why you need to run manually a cvs login.

I think the difference in result of your command and our comand is that you don't run it in
the continuum working directory and you don't use the exactly same cvsroot

> Continuum ignores .cvspass
> --------------------------
>          Key: CONTINUUM-481
>          URL:
>      Project: Continuum
>         Type: Bug
>   Components: Core system
>     Versions: 1.0.1
>  Environment: TortoiseCVS 1.8.22
> Microsoft Windows Server 2003 SP1
>     Reporter: Matthew Beermann
>     Priority: Critical
>      Fix For: 1.0.2

> Continuum seems to ignore the .cvspass file while building my projects, resulting in
the error: "Empty password used - try 'cvs login' with a real password". Note that our CVS
repository does not have anonymous access, nor does it use the "anonymous" account.
> I see these two lines in the log, which look suspicious:
> 31321 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager  - passFile: C:\Documents
and Settings\Default User\.cvspass
> 31321 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager  - cvsroot [CENSORED]
already exists in C:\Documents and Settings\Default User\.cvspass. SKIPPED.
> ...what the heck? I don't want it to skip that password, I want it to USE that password!
This behavior seems completely wrong to me. Note that running a "cvs checkout" command from
the command line works just fine.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message