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

[Subclipse-users] Possible automatic locking bug subclipse starting from version 1.1.10 and higher

From: Hugo de Oude <HdOude_at_allshare.nl>
Date: 2007-03-29 12:10:14 CEST

I want to report a (possible) automatic locking bug within Subclipse as per version 1.1.10. I did check the Issue tracker, and could not found this bug reported yet.

We are use to work with the property "svn:needs-lock=true". Therefore we added the following into the reqistry on all developer machines:




We work with MyEclipse (version 5.1). Currently we are forced to work with subclipse version 1.1.9, because as per 1.1.10 the needs-lock property doesn't work any longer for new files.
We also tried version 1.2.0, and in here the same problem exists.

PROBLEM description
Although the svn:needs-lock=true is set in the auto-props section for all our files, new files won't get a lock automatically.
First we create a new Java class.
When finished we commit the Java class into the repository.
As a result the property needs-lock = true should be created automatically. Since this is described in the auto-props section.
However as per version 1.1.10 this doesn't work any longer.

Instead we need to set this property manually again for new files/packages etc. For existing files/packages/etc we don't have any problems.
You can also see this behaviour by the icon overlay which is used. After committing a new file the icon overlay shows a instead of an icon.
Here is an example. One these committed files (the last one) is new, and that one doesn't have the property needs-lock=true set.
So the icon overlay shows a yellow barrel ( ) instead of a locked sign ( ) for this new class:



So each subsequent change on the new class TestSubclipseLocking doesn't require a lock in subversion repository. This is not convenient for us.

For now our entire development team had to switch to subclipse version 1.1.9 because of this problem.

Other information:
IDE = MyEclipse 5.1
Operating system = Windows XP
The release and/or revision of Eclipse = Eclipse 3.2.1
The release and/or revision of Subclipse = 1.1.9 (because 1.1.10 and 1.2.0 do have this locking problem)
The client adapter used (JavaHL or JavaSVN) = JavaHL
The protocol used (file://, svn://, http:// etc.) = http://


It would be great if this bug is fixed in the new subclipse release.
Please let me know if you need additional information from us to describe this bug.

Cheers,
Hugo de Oude
Received on Thu Mar 29 12:20:33 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.