Eclipse + Local CVS + PyDev

Question

I tried several IDEs in Python (on the Windows platform), but finally found only Eclipse + PyDev to suit my needs. This toolbox is really convenient and easy to use. I am currently working on a larger project. I would like to be able to use CVS or any other version control system that will be installed on my local hard drive (I recently moved to my home and did not yet have Internet access.)

It does not matter to me whether it will be CVS - it could also be any other version control system. It would be great if it would not be difficult to configure with Eclipse. Can someone give me some possible solution? Any clues?

Regards and thanks in advance for any tips. Please forgive my English;)

Answer 1

The last time I tried this, Eclipse did not support direct access to local repositories in the same way as the cvs command line does, because the cvs command line has both client and server functionality, while Eclipse has only client functions and should pass (for example) pserver, so you probably need to start the cvs server.

It turns out that I really did not need it, since Eclipse stores its own history of all changes, so I only needed to manually update cvs at the main stages.

[In the end, I decided not to use cvs at all with Eclipse under Linux, as it got confused in the symbolic links and started deleting my included files when it was “synchronized” with the repository.]

Answer 2

If you don't mind switching to Subversion, Eclipse has a SubClipse plugin.

Answer 3

I tried Eclipse + Subclipse and Eclipse + Bazaar. Both work very well, but I found that the Tortoise versions of these version control tools are so good that I left the Eclipse plugins. On Windows Tortoise XXX is my choice. They integrate with the shell (Explorer or TotalCommander), change the overlay icon if the file is modified, shows the log, compares the changes, etc. Etc.

Answer 4

As others have pointed out, there are plugins for Eclipse for SVN, Bazar, Mercurial, and Git.

Despite this, despite their presence, I believe that using the command line is most convenient.

svn commit -m 'now committing' 

Assuming that you do not commit more than a few times a day, this should work reasonably well. Is there anything specific that is stopping you from using the command line?

Answer 5

I would definitely recommend switching to another VCS — I prefer Mercurial , as well as a lot of the Python community. This way you can work locally, but you can still post your changes to the world later.

You can install TortoiseHg for Windows Explorer, and MercurialEclipse for Eclipse.

There's even Mercurial for CVS users to help you change, and a list of commands with more equivalence .

Answer 6

I believe that Eclipse has built-in CVS support - or at least it was when I last used it a couple of years ago.

For more information on how to use CVS with Eclipse, see the Eclipse CVS FAQ

Answer 7

I recently moved to my home and did not yet have access to the Internet.

CVS and SVN are centralized version control systems. Instead of installing them on your local system to control only one version, you can use DVCS such as Mercurial or Git.

When you clone a Mercurial Repository, you have literally all versions of all repo files available locally.

Answer 8

I am using Eclipse with a local CVS repository without problems. The only catch is that you cannot use the ": local:" CVS protocol. Since you are running Windows, I recommend installing TortoiseCVS and then setting up the included CVSNT server as follows:

• Control Panel: CVSNT
  • Repository configuration: create a repository and publish it
  • Pay attention to the server name and make sure it matches your hostname
• Eclipse: create a new repository location using type: pserver: connection and point it to the local host name

This (or any real source code management system) has an advantage over the local Eclipse history of being able to associate validation comments with changes, group changes in change sets, etc. You can use Eclipse Local History to recover from minor errors, but this does not replace source control (and also ends: see Window-> Settings General-> Workspace-> Local History).