[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Any way to re-map working copy?

From: Dennis Forcier <dmforcier_at_gmail.com>
Date: Mon, 5 Jan 2009 16:36:45 -0500

Repository is set up as
/repositories
 - /proj_X
 - - /trunk
 - - /branches
 - - /tags
 - /proj_Y
 - - /... etc

I had a monolithic Eclipse project in proj_X which in Eclipse I've split up
into three, and renamed the original. All three Eclipse projects will
continue to reside in repository proj_X/trunk. Several questions regarding
how to deal with this in Subclipse/SVN.

First, I created a new project that wasn't "shared" and copied in all the
code for it. Then I did Team.Share on the new project, established a folder
in the root of proj_X for it and committed all elements. Unfortunately it
should have been established in proj_X/trunk. In the SVN Repository
Explorer perspective I moved the project from root to trunk. Now I want to
commit some changes but can't use commit because the folder the project is
mapped to isn't there any more. How do I tell it to commit to the different
location, or re-map it? I tried Branch/tag but it errors because it wants to
establish a new folder and there is already one there.

Second, on the renamed project it is still mapped to the old folder. In
Eclipse Package Explorer I see for the project title New Name [trunk\Old
Name] and commit shows that it is still mapped to the non-existent folder.
If I use Move/Rename on the old folder in the SVN Repository Explorer
perspective, it seems I'll have the same trouble as the first since the
mapped folder won't be there any more.

I'm the only user on the repository.

-- 
Dennis
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1006098
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-06 14:06:28 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.