Kevin Duffey <supreme_java_guru_1@yahoo.com> wrote on 09/13/2005 03:43:47
PM:
> 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.
This is all done by Subversion. When folders that are under control of
Subversion just get deleted in the filesystem the working copy becomes
corrupt. You need to get the classes folder out of your repository.
Checkout your project outside of Eclipse and run svn delete to delete that
folder and then commit.
Then re-checkout inside Eclipse. When the classes folders is recreated by
the build, add it to the svn:ignore property of the WEB-INF folder and
commit that change.
Then have everyone re-checkout.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Sep 14 06:11:37 2005