Karl Auer <kauer@biplane.com.au> wrote on 02/08/2006 09:01:42 AM:
> On Wed, 2006-02-08 at 08:37 -0500, Mark Phippard wrote:
> > The main gotcha is just to make sure you do it the way you described.
> > Create all of the new packages first and do Team -> Add so that the
> > underlying folders are part of the Subversion working copy. You do
not
> > need to commit, just do the Add step.
>
> The projects are already under SVN control, won't Subclipse pick the new
> folders up anyway and offer to version them? The thing is that I will be
> creating packages like ch.ethz.id.kom.dk.blah, which in Eclipse results
> in a directory structure seven layers deep - that's a lot of directories
> to add manually. Hm - maybe Eclipse just does the right thing with such
> trees, and Team->Add of the package adds the whole tree...?
The issue is that if you have not added them to version control, and then
you attempt to refactor into thoe packages the svn move command will fail
because the folders are not under control.
If you use the Navigator view and select the "ch" folder and do Add, it
will add everything under it as well.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Feb 8 15:04:53 2006