Re: [Subclipse-users] Subclipse prevents refactoring

> > svn: Cannot copy or move 'XXX' it is not in the repository yet;
> > try committing first
> > It might be that there are technical problems that have to be solved,
> > but committing (as proposed) is not acceptable, since this would mean
> > to commit a source code that is totally screwed

Committing stuff that's screwed is not a major problem really - just
make sure your commit message says "don't use this revision" and says
why.

You could also do it the way vendor branches are handled (look in the
book under "Vendor branches"): Copy your working directory out to a new
(unmanaged!) location, modify it there until you are happy with it, then
copy it back over your working copy. New stuff will be automatically
detected at commit time, modified stuff too, but you will have to
manually do a Team->Add on any new directories and such. Then commit. If
there are re-used directory names or re-used names in there, then there
is really no way around doing interim commits.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (w/h)
http://www.biplane.com.au/~kauer/                  +61-428-957160 (mob)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org