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

Re: [Subclipse-users] renamed workspace directory - svn history doesn't work

From: Steve Cohen <scohen_at_javactivity.org>
Date: Wed, 05 Aug 2009 22:07:41 -0500

This worked, thanks.

Not sure why it worked, as I looked at the .syncinfo files before
deleting them and I could not see the old path names or anything like a
local filename there, but it did work.

Mark Phippard wrote:
> Maybe try this?
>
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=868799
>
>
> On Wed, Aug 5, 2009 at 4:46 PM, Steve Cohen<scohen_at_javactivity.org> wrote:
>
>> I renamed the directory name of my Eclipse workspace to one that was
>> more descriptive of the workspace's function. This hasn't seemed to
>> affect anything except the Team->Show History function which now fails
>> with the error
>>
>> 'c:\{old directory name}\path\to\source\file\directory' is not a working
>> copy
>>
>> No such file or directory
>> svn: 'c:\{old directory name}\path\to\source\file\directory' does not exist.
>>
>> And yet, I am able to synchronize with the repository, update, commit,
>> etc. from this Eclipse workspace.
>>
>> What is going on here and/or where in my workspace is this old name
>> being persisted? How can I fix this?
>>
>> By the way, using Subversion Client Adaptor 1.6.0.2 and Subversion
>> JavaHL 1.6.3
>>
>> ------------------------------------------------------
>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2380626
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>>
>>
>
>
>
>

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2380684

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-08-06 05:08:10 CEST

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

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