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

Re: feature request: replace with -> base revision

From: Christian Sell <christian.sell_at_netcologne.de>
Date: 2005-08-05 19:17:25 CEST

I would like to confirm what Eugene said about the eclipse CVS plugin. When I
first came to Eclipse after having used CVS on the command line and through
siple GUI clients (WinCVS of course), I was rather annoyed by the high-level
abstractions that eclipse offered which found hard to map to the familiar CVS
semantics. I think the term "synchronize" bears witness to this, which is
completely alien to CVS terminology.

I must also say, however, that Subclipse is the only plugin I know that makes
use of most of the framework functionality offered by the Team plugin. For
example, both available ClearCase plugins are in many respects just adapters
for the underling CC commands and tools. None of them makes use of the
Synchronize view.


Zitat von Eugene Kuleshov <ekuleshov@gmail.com>:

> On 8/5/05, Mark Phippard <MarkP@softlanding.com> wrote:
> >
> >
> > > I'd disagree with you on this. Actually CVS itself doesn't really have
> >
> > > anything like update with, or synchronize. It is Eclipse UI which is
> > trying to
> > > unify common VCS operations under single UI and that would be quite
> > convenient
> > > for the users who have to deal with more then one VCS at the same time
> > (I see
> > > both CVS and SVN as very common case). Unfortunately Subclipse currently
> >
> > > trying to mimic TortoiseSVN UI, probably for historical reasons or
> > because of
> > > preferences of the developers.
> >
> > I think you are overstating this a bit. I have used several different SCM
> > providers in Eclipse and they all have their own ways of doing things. I
> > would agree that at some level the Eclipse developers are trying to create
> > something generic that others can reuse, but let's face it, they are still
> > doing what serves their own needs first.
> Heh. You are right, but I believe that is only because none of the VCS
> vendors like to perticipate and encourage Eclipse team plugins to be more
> flexible.
> I am sorry that you view our UI as unfortunate, but I think it is a big
> > improvement over the CVS UI in most places and entirely appropriate as the
> > UI for a Subversion SCM provider.
> >
> I didn't mean to insult you or anything. Current UI is completely fine from
> the Subversion point of view. I'm just trying to say that it is quite
> annoying to have two parallel and yet completely independent and unsimilar
> sets of menu layouts for two such commonly used VCS providers, especially
> for those who have to deal with both of them at the same time (like I do).
> That is why I tried to vote for unified repository and synchonize views (to
> have all VCS providers in same tree) as well as for unified resource history
> view (to get automatic context switching when jumping between differently
> shared resources)... can't remember all Eclipse enh. requests at the moment.
> --
> regards,
> Eugene

Christian Sell
Received on Sat Aug 6 03:17:25 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.