I and the other people in my group are using subclipse and the
openlaszlo eclipse extensions/plugins (ide4Laszlo). Once in a while when
I use subclipse it cannot access a file. If I force eclipse's garbage
collector to run by using the "MemoryManager for Eclipse" then
subclipse can access the file.
I assume what is happening is that some other thread/plugin has opened a
file then deleted a file object. I think the file object is halfway
closed at that point. It doesn't have a window open but it won't close
the file until the file object is garbage collected. Subclipse sees the
file as being closed and tries to access it. The access fails when
subclipse is halfway through an operation.
This is a problem because sometimes this causes us to have bad checksums
and we then must checkout a new copy of the project. Then merge any
local changes into the checked out files to avoid potential conflicts.
Throw away the first set of files with the bad checksums. Then
commit.the second set. This is a real pain. Also I don't know if this is
going around subversions all or nothing approach to commits. If so we
may end up with half the changes checked in which would be bad.
So my questions are:
Does anyone know of a way to automatically force garbage collection when
subclipse runs.
or
Does anyone know of an easier way to recover when we get a bad checksum.
or
Is this considered a bug in subclipse that can be fixed in a future release.
Of some combination of the above.
Thanks,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jun 2 18:02:40 2006