Alexis Gallagher schrieb:
> Hello everyone,
> Thanks for all the input regarding subclipse vs the cvs client. I'm
> going to give it a try. CVS administration is something I've always
> hoped I could avoid learning, like perl, so I'm hopeful that
> subversion will actually let me get a way with this.
Full ack! Knowing svn I even tried to avoid learning cvs usage.
> BTW, the problem I was starting subclipse disappeared when I upgraded
> to eclipse 3.0.1 instad of 3.0.0.
> I notice a lot of the subclipse documentation is a little thin. As I
> am going to be learning some of these commands for the the first time,
> and teaching them to people on my team with less of a background than
> me, it would fit into my existing responsibilities if I contributed
> new documentation myself -- as long as there's not too much overhead
> for me getting in the loop administratively. Is that easy to do? I
> suppose I should direct this to the dev list instead...
Maybe the subversion book http://svnbook.red-bean.com/ can explain the basic concepts while
subclipse then is pretty self-explanatory.
P.S.: Both the persons on the subclipse and subversion mailing list are a really great community.
Mostly ultra quick high quality feedback and a nice air.
> On Wed, 9 Mar 2005 11:13:15 -0500, Mark Phippard <MarkP@softlanding.com> wrote:
>>Alexis Gallagher <firstname.lastname@example.org> wrote on 03/09/2005 06:31:16
>>>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
>>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
>>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
>>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.
Received on Thu Mar 10 23:37:19 2005