Reinhard Brandstaedter <reinhard.brandstaedter@ams-engineering.com> wrote
on 07/18/2005 10:19:55 AM:
> >>And how is subclipse involved in this then?
> >
> >
> > The way this works is that whenever a tool is about to open a file for
> > edit, it is supposed to call an Eclipse API method called
validateEdit().
> > This method is passed through to the team provide to decide whether to
> > allow the edit, present any UI etc... There is another API involved
> > called a ResourceRule which is where the decisions are made whether
> > anything needs to be done or not. We are just using the default
> > implementation of this that comes with Eclipse. This default
> > implementation makes its decision based on whether the resource being
> > edited has the read-only attribute set or not. So that is what is
really
> > being checked, not the Subversion needs:lock property. We chose to
use
> > this technique as it is more efficient and the only files in a
Subversion
> > working copy that should have the read-only attribute set are those
which
> > have the needs:lock property set.
>
> Ok with that said I looked for read-only attributes in the checked out
> repository. As expected none of the files has this attribute set. But
> what I found out is that Windows XP seems to set the read-only attribute
> on every folder on the whole drive. It's not possible to remove the
> read-only attribute from the folders (even as administrator). Could it
> be the case that Software Architect asks for the properties of the
> folder and not the file and thus issues an lock request?
>
> I'm also forwarding this to IBM support.
This feature really comes from Eclipse, not Software Architect. The help
from Eclipse says this:
"Default implementation of IResourceRuleFactory#validateEditRule. This
default implementation returns a rule that combines the parents of all
read-only resources, or null if there are no read-only resources"
It does mention something about "parents" but I never took that to mean
the folders. Maybe the fact that the folder is read-only is triggering
whatever check is being done.
I would at least expect this to be consistent. If all of your folders
have this flag, then I would think that the simple case of editing a piece
of Java source would also show this behavior.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Jul 19 00:33:51 2005