[news.eclipse.tools] Re: M4 - problem connecting to a local cvs reposito

[Scott Eade <seade@xxxxxxxxxxxxxxxxxxxx>]

Hi Bob,

I have an empty passwd file in the CVSROOT directory of my cvs repository -
I read somewhere that this will make cvs use the system passwords.

I can connect successfully to repositories located on other machines and I
can connect to my local repository from the shell using pserver and my
system password (interestingly I can do this even when the CVSROOT/passwd
file doesn't exist).

I think I have tracked the problem down.  When I originally entered the path
to the repository into Eclipse I entered one of the characters in the wrong
case.  Try as I might, I can't change this in Eclipse (it keeps trying to
help me by providing the incorrect value and it won't let me replace it).
I'm using Mac OS X which has a case-preserving, but case-insensitive file
system, but it seems that inetd is discarding the request because it is in
fact case-sensitive.  I have just tested this at the command line and yes, I
cannot connect from the shell if the case of the repository path is
incorrect.

As I see it I now have two solutions:
1. Figure out how to clear or edit the cache of repository paths being
maintained by Eclipse.
2. Change the inetd.conf for the machine so that the cvspserver line
includes the typo

The preferable solution is to fix the Eclipse cache - anybody know how to do
this?  Depending on whether or not I receive any responses I may post this
as a new question - many with a clue as to the answer may not have read this
far ;-)

Thanks,

Scott  

On 9/01/2003 12:51 PM, in article avina6$iou$1@xxxxxxxxxxxxx, "Bob Foster"
<bob@xxxxxxxxxx> wrote:

> Yeah, sure. Do it all the time. I don't remember anything special, but what
> takes the place of cvs login in eclipse is when you add a repository and
> specify the location, your cvs user name and password. In that wizard, it
> tries to make a connection when you click next. If this doesn't work, you've
> specified something wrong. If it does, there should be no further problem.
> 
> (Is the problem you don't have a passwd set up?)
> 
> Bob