continuum-dev mailing list archives

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

Matthew Beermann commented on CONTINUUM-481:

Well, then, I would put it this way:

When you run "InstallService.bat", Continuum uses the default service settings (Log On As:
Local System), which corresponds to the "Default User" account. So far as I know, it's not
possible to actually log in to that account, meaning there's no way to run "cvs login", meaning
there's no way to get the correct registry keys in place.

So really, when you're running with CVSNT, you should run the Continuum service as a real
user, and make sure that user has issued the appropriate "cvs login" command. Could a documentation
note to that effect be added to the site?

> 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