I think I found the source of this problem, unfortunately it is in
Eclipse. I entered a bug and a patch with them.
I suspect that the reason this problem suddenly "cropped up" is that
either Subversion or JavaHL started canonicalizing all of their paths. So
when we run svn status, the paths we get back are the canonical value.
When we try to convert them to resources to add them to the cache, Eclipse
gives back a null resource because internally it is doing an exact string
compare to see if it is a workspace resource.
Since there is apparently no way for us fix this problem, I am going to
look into adding some code in the UI plugin to check for when the problem
exists, and then put that code in the Checkout and Create Repository
actions. Hopefully, we can then inform the user of the problem and let
them correct their workspace before they start doing anything with
Subclipse. That should help nip this in the bud.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Jun 18 05:56:23 2005