Do not copy SVN working folders to another location in project

This one has had me tearing my hair out - until I discovered what the issue was:

Scenario

• I copied a folder from one folder to another folder in my working copy for a project
• I subsequently committed the whole project (a few days later) (seemed to commit ok)
• After committing the project, I noticed that when I performed an update, it was showing that the files in the old folder had been updated. - This was strange, as no-one else had access to the repository at the time
• Another colleague started working on the project, but the folder I had copied, did not appear when they performed an update - indeed, it did not appear to be in SVN at all.
• When I checked the source folder, I could see that this contained the copied (and edited) version of the files - rather than the original files.
• I then checked the SVN properties of the copied files in Eclipse - and it was clear that the SVN URL of the copied files was the same as the source files!

What Happened:

Resolution:

• I deleted the copied folder, and recreated it.
• I then copied the files from the original folder (these were the ones that had been edited as my edits to the copied folder had been checked in over them)
• When I then performed an update, Subclipse correctly identified them as New - and I was able to commit them to the repository in the correct location.
I then also had to go back to the source folder, retrieve the previous version of the files, and re-commit them.

Fortunately this was noticed relatively quickly - and only affected a small number of files - otherwise it could have been quite a nightmare to resolve!