Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 281719

Summary: CVS does not support local repository
Product: [Eclipse Project] Platform Reporter: Bobby <robertl>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: remy.suen
Version: 4.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Bobby CLA 2009-06-26 17:17:02 EDT 
Build ID: 3.4.1

Steps To Reproduce:
When I go to checkout or place a project into CVS using Eclipse, I cannot choose a local repository.  

Local repositories have a different CVS protocol defined in the "Root" file in a CVS folder:  ":local:<path to repository>" as opposed to say the extssh protocol that only Eclipse seems to support: "extssh:<username>@<cvs server host>:<path on host to repository>".

Because the CVS plugin in Eclipse supports only accessing a repository via a server, if you don't have a server installed, you can't get to the repository.  So in this case, if you setup a cvs server (pserver) that repository is open to everyone unless you lock it down with authentication.  To keep the username/password secure, you have to use an SSL connection to the server and thus you need the "extssh" protocol in Eclipse.

If we had the ability to use a local repository (which CVS supports), I think it would be much more helpful and less dependent upon configuration of other tools.

More information:
Comment 1 Remy Suen CLA 2009-06-26 18:42:20 EDT 
Bug 6892?
Comment 2 Bobby CLA 2009-06-29 10:37:07 EDT 
Yes - apparently I didn't search through the bug database thoroughly.
This is a duplicate of bug 6892.
Apparently that "bug" has been around since 2002 and no-one is addressing it.
Why is that?
Is it too difficult to implement?  It would seem that if you want to use a local repository, you choose that option, then get asked to point to the cvs executable on your system to send commands to...

*** This bug has been marked as a duplicate of bug 6892 ***