Hi All. I recently downloaded eclipse 3.0.1 to my windows 2000 machine and am trying to access an already existing CVS Repository on a red hat linux installation.
I was able to get to the repository using ssh2 and once checked out all the files. When I tried to open a .java file, it came up as 'Read-Only'. The problem is I just cannot seem to get around making it editable. My goal is to get the remote CVS working w/the local Eclipse installation.
I know there is a feature in the Preferences menu to get to the CVS Perspective options. I tried enabling the "Configure projects to use Watch/Edit on checkout" and then checked out the top level directory again, reopened the same file but it was still Read-Only and it would not let me edit it.
I have the following questions: 1) How do I make a file Writeable in this situation? 2) Can I check out individual files also OR does Eclipse allow only directory based checkouts (maybe this is a CVS limitation, not an Eclipse one - I am not sure)
Himanshu, You are correct that Eclipse only lets you check out a full project. As you noticed, you can view a file. This is helpful in determining whether you really want to check out the project. Eclipse doesn't let you edit the file (hence it is read only) because you will not be able to check it back end.
As far as I know, this is not a CVS limitation. From an Eclipse point of view, what would Eclipse do with the single file it checked out? It would need to put it in a project somewhere.
I understand that the user has to checkout the entire project at the beginning. The question really is:
I want to use Eclipse on my local machine to integrate w/a Linux backend. The code is in CVS on the Linux box. How can I checkout the code files, make my changes, and check them back in to CVS? Are you saying that a developer cannot commit his changes back to CVS with eclipse? If thats the case, then how does source controlling work w/Eclipse?
author & internet detective
Originally posted by Himanshu Jhamb: How can I checkout the code files, make my changes, and check them back in to CVS? Are you saying that a developer cannot commit his changes back to CVS with eclipse? If thats the case, then how does source controlling work w/Eclipse?
Himanshu, I definitely didn't mean to imply that you can't commit changes back to CVS. I meant that you can't commit changes if you don't check out the project. The process is: 1) Check out project from stream (such as head stream) 2) Make changes 3) Team --> Synchronize with stream 4) Release changes
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com