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

Re: [Subclipse-users] More compliance with CVS sync view behaviour

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-06 22:31:43 CET

Aaron Digulla <digulla@hepe.com> wrote on 03/06/2006 04:22:33 PM:

> Mark Phippard wrote:
> >> would it be possible that the Subclipse Synchronize View does not
> >> automatically merge when "Update" is invoked on a folder? The CVS
> >> Synchronize seems to exclude files upon "Update" that are
> >> instead of merging them, and that's very convenient, IMHO...
> >
> > We do not have any way of providing a feature like this.
> The synchronize view really depends on being able to do the repository
> operations outside of the tool. I'm not sure how the CVS plugin guys
> pulled it off but I get the feeling that they duplicated some of CVS's
> code in Eclipse.

CVS has no API, that was always one of its biggest drawbacks. Eclipse
basically wrote a CVS client from scratch by reverse engineering. This is
why it used to wreak havoc if you used a different CVS client on the same
workspace project. It may still for all I know. It is also why Eclipse
is susceptible to breakage when new CVS server versions are released.

> With the JavaHL code, it should be possible to replicate a lot of the
> SVN operations locally. But I guess that's daydreaming because it would
> be too much effort.

The JavaHL code basically exposes the same things you can do with the
command line. There is nothing that lets you go off into your own little
space and start manipulating files.

> OTOH, I guess that a lot more people would like the synchronize
> functionality which Eclipse offers in other tools (Turtoise, Netbeans,
> IDEA), so maybe it would be worthwhile to bother the SVN developers to
> offer more support (like a status command which returns all the
> necessary information which you need to implement a proper sync view).

I am not sure what you are referring to here. The svn status command
already provides what we need, at least as of Subversion 1.3. The
question here was about Update. Basically, wanting us to have it skip
certain files. The only way we could do that would be to provide the
update command with the specific set of files to update, and then not
include files that were conflicted. Except for the last part, this is how
the code used to work and it was terrible. It was a lot slower, but more
importantly since only the files are specified, the folders are never
updated which causes problems later if you have a need to commit a folder
change of any kind.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Mar 6 22:32:09 2006

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.