Re: [Subclipse-users] Problems when moving workspace

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-09-11 13:43:17 CEST

On 9/11/07, B Smith-Mannschott <bsmith.occs@gmail.com> wrote:
>
>
> On 8/28/07, Mark Phippard <markphip@gmail.com> wrote:
> > On 8/28/07, patric@mainlan.de <patric@mainlan.de> wrote:
> > > I am using Eclipse 3.3 and Subclipse 1.2.4 and I am having problems
> > > when checking out from svn using subclipse and when the workspace gets
> > > moved to a different directory.
> > >
> > > Subclipse seems to be not able to resolve the new path, it just points
> > > to the old one (for example when using "Show History"):
> > >
> > > svn: Cannot read from to
> > >
> 'E:\IDE-3.3\workspace\myproject\src\path\to\the\sources\.svn\format':
> > > path refers to directory or read access is denied
> > >
> > > (the path printed above is the old one)
> >
> > I have never known workspaces to be portable. Eclipse itself stores
> > stuff in the workspace that does not like to be moved.
>
>
> This has not been my experience. Granted, I'm careful to use workspace
> relative references to resources when possible, but I often copy, rename, or
> move workspaces aside and have never had significant problems doing so
> before eclipse3.3+subclipse. I've even, on occasion copied workspaces form
> one machine (linux) to another (mac, windows) and had few problems.
>
> > For Subclipse, the cache probably has paths in it. Did you refresh
> > everything after you moved the workspace? I would expect that to
> > trigger Eclipse to update the caches.
> >
>
> I've seen the same behavior described by the OP and I have both refreshed
> and done a "clean" of all projects, but the error messages from "SVN"
> remain.
>
> The "SVN Interface" selected in my case is SVNKit. JavaHL is not available
> in my case, presumably because my subversion build is 64-bit while the
> eclipse I'm running is 32-bit. (I use a 32-bit eclipse because it requires
> significantly less memory and seems more stable with the oXygen plugin).
>
> This change in behavior is irritating because it breaks my workflow. It also
> seem gratuitous since the problem did not previously exist. Have you got any
> other ideas for a workaround? Is there a way I could clean out the caches
> manually?

What do you mean by did not previously exist? The cache has not
changed since the early 0.9 releases a couple years ago.

I find that deleting the files named .syncinfo from the
workspace/.metadata also works as that removes the cache files.

--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org

Received on Tue Sep 11 13:39:54 2007

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