Did you do this by doing copy & paste? If not, I wonder if that is what
the refactoring operating does? Anyway, copying folders with copy & paste
does not work and causes problems. Eclipse does not have any method for
our code to get invoked when this happens. What winds up happening is the
".svn" folder gets copied along with the folder. So the target folder
becomes a mini-working copy pointing back to the original location. In the
new working copy, it looks like a new folder to its parent folder, so it
tries to add it. This fails when Subversion discovers the .svn folder
inside it already.
You can manually fix the problem by deleting the .svn folder after the copy
happens. Then it should add ok. Note that this will not be treated as a
Subversion copy, meaning there will be no history. If you want that, you
would have to copy the folder using the Branch/Tag option. Then specify
the URL of the target project location. This would do the copy in the
repository. If you then run update on the target project in your WC, it
will pull down the code from the server.
There is an open Eclipse bug to add a hook for this in Eclipse so that we
can do it as part of the copy/paste routine.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Fri Nov 4 12:43:58 2005