|Re: Why does one Eclipse instance think a particular workspace's .metadata folder is read-only? [message #1728323 is a reply to message #1728316]
||Sat, 02 April 2016 00:15
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 04/01/2016 03:34 PM, David M. Karr wrote:|
> I'm running on CentOS7.2. I have a handful of different Eclipse
> installations, along with workspaces I used with those installations. I
> use a separate Eclipse installation for the workspace just to ensure
> they are independent (if you were wondering).
> I'm often running multiple instances of these at the same time.
> Today I noticed that when I tried to open one of the workspaces I was
> working with yesterday, it says 'Internal error: The folder
> "<workspacelocation>/.metadata" is read-only.' I've been using several
> of the other workspaces, and I haven't seen this problem.
> This is very odd. I just compared the perm bits of this particular
> .metadata folder with the perm bits for a workspace that I'm not having
> this problem with, and they are identical. I also tried creating both a
> file and a folder in that location, from outside of Eclipse, and it
> worked fine.
> When I first saw this and couldn't figure it out, I closed everything
> down and rebooted, and started up that instance as my first operation.
> Same error.
> Any ideas why this might be happening?
But, you didn't attempt to open workspace from an instance of Eclipse
that another instance of Eclipse already had open, right?
Powered by FUDForum
. Page generated in 0.03022 seconds