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

Re: [Subclipse-users] Re: Revert on a project is too slow

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-09-18 21:38:39 CEST

On 9/18/07, Zach Bailey <zach.bailey@hannonhill.com> wrote:

> I was trying to come up with a plausible scenario based on my admittedly
> ignorant and baseless understanding of how the Eclipse local history
> might work. I have tried googling around to figure out if there are any
> programmatic ways of interacting with Eclipse's local history but have
> come up empty. From the sounds of it, the way Subclipse is currently
> handling the preservation of local history is by somehow tricking
> Eclipse. Is this workaround being used because of some shortcoming in
> Eclipse or Subversion, or just because it was the easy way to do it?

We only started preserving it with 1.2.4. See:


It has links to relevant discussions. Eclipse CVS is written not just
as a Java application, but even as an Eclipse application. Meaning, I
do not think it even does much pure Java I/O, but instead does
Eclipse-based I/O. So when it does the equivalent of reverting a file
it is using Eclipse code to do it which can allow things like history
to be captured. When Subversion does a revert, it happens in the SVN
library. Eclipse only learns of the change after it happens.

Eclipse does not have an API to take a snapshot of a file. That would
have been the ideal solution. So the suggestion the Eclipse team made
was to null out the file using an Eclipse API so that Eclipse would
take a snapshot. Details are all in the linked bug.

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Sep 18 21:38:46 2007

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.