[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subclipse vs. built-in cvs client

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-03-09 17:13:15 CET

Alexis Gallagher <alexisgallagher@gmail.com> wrote on 03/09/2005 06:31:16
AM:

> What are the main features missing from subclipse compared to
> eclipse's built-in cvs client? For instance, does subclipse use the
> same screen for resolution of merge conflicts? Or is it the case that
> subclipse has the same main features now, and the main difference is
> stability?

CVS and Subversion are ultimately very different. Subversion mimiced the
CVS command set to help people transition but the products are very
different, and that is going to come through in any UI you use. That
being said, Subclipse tries to emulate as much of the CVS Eclipse UI as
possible. It does use the built-in Eclipse compare/merge facilities, the
same as CVS.

The Synchronize view is a big part of the CVS integration with Eclipse.
That feature mostly works in Subclipse, but it is an area that is still
being developed. There are just a few nagging problems with refreshing
the view correctly after you do something.

> I tried to answer this question myself by just installing subclipse
> and kicking it around, but I get an error whenever I try to open the
> subclipse perspective or configure it from preferences (I'm running
> M3, and the error dialog says subclipse is unable to load its ui
> classes). So unless I am just unlucky, I assume stability is already a
> big difference.

Personally, I think Subclipse is very stable. I never have problems using
it. I also do not think the Eclipse CVS support is as stable as everyone
wants to make it out to be. I have personally had problems when I applied
a CVS security fix on my server and Eclipse just stopped working until
they caught up with their own fix. My biggest problem now is that
whenever I use CVS with tigris.org it takes at least 2 tries to complete
any operation, and I cannot browse the repository (I think because there
are too many modules).

The #1 issue with using Subclipse is that it requires that you have native
Subversion code on your system, specifically the JavaHL library and its
dependencies. For Windows, we are able to ship these in a plugin, but for
Linux or OS X you have to get them elsewhere. There is an easy to install
version available for OS X that works 100% of the time, but for Linux it
can be a real pain. You pretty much have to build Subversion and JavaHL
from source to get the libraries.

There is a 100% Java alternative you can try as well. You download it
here:

http://tmate.org/svn/subclipse.html

It removes the burden of having to get JavaHL installed, and offers good
performance. That being said, it also brings is own stability issues to
the table. Most people seem to be having good success with it though.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Mar 10 03:13:15 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.