Hey all, Mark,
I don't know why this happens, but I'll check out my
project from SVN just fine, and at that point, I can
do a team update anywhere in the tree (in navigator
view) and it works fine. When I do a full clean build
of my project, I am guessing it must remove some
folder or something that might be in subversion. From
after that point, when ever I try to do an update I
always get a pop up dialog saying "..ClientException:
Working copy not locked; this is probably a bug,
please report svn: working copy 'C:\Program
Files\Java\Eclipse\workspace\trial\src\web\WEB-INF\classes'
is missing or not locked
So thinking about this, it's obvious the
WEB-INF\classes shouldn't be in subversion because its
generated via our build, however for some reason I
have it in there. When I do a full build, it wipes out
anything in the /classes directory to do a clean
build. I think the reason I included it was that I
generally wasn't creating the /classes dir in my build
script.
Anyway, this makes it impossible for us to update
anything. While I can somewhat understand why it may
occur, it kind of sux that it prevents all the other
dirs from being updated. It's as if subclipse (or
subversion?) goes through all dirs first looking for
locks, then goes to the server. We now have to click
on about 8 different locations and do updates since we
can't just update the whole project in one shot.
Any help on what I may do to fix this would be
appreciated.
Thank you.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Received on Wed Sep 14 05:43:47 2005