Xcode4 and the darn SCM

I have

• project A (old),
• project B (new), and
• project C (new).

I want to use a few classes from project A in the new projects B and C.

• Project A is under source control (Subversion).
• Project B is under source control (Subversion).
• Project C is not under source control.

When i copy files from project A to project B an开发者_如何学运维d project C, the subversion reference doesn't change. Meaning, changes to the files are reflected in project A as well. Also, i don't want the files copied into project C to be tied with project A's subversion repository. How can i do that? I don't see any way to get rid of that damn svn status from Project A's files (in Project B or C).

The best way to achieve this with Xcode's current SCM integration is not to fight it (by mixing project members). Instead, consider placing your disparate projects together within the same workspace. Read up on Xcode's new Workspace feature - projects share the same build folder and interdependencies are (usually) automatically recognized between projects.

I was able to fix my problem by deleting the .svn folders. Maybe this'll help someone else who stumble across this post.

http://www.hacktrix.com/how-to-delete-svn-folders-from-your-project-on-windows-linux-and-mac

p.s. Subversion integration with Xcode4 is bad. At it's core, Xcode3 used to work great with Subversion. The feature that i miss the most is the export (a copy of your source that's not tied with the source-control e.g. subversion).