On 16-Mar-06, at 8:56 AM, Mark Phippard wrote:
> Scott Palmer <firstname.lastname@example.org> wrote on 03/16/2006
>> I've been getting this error for a while now... using Eclipse 3.1
>> and Subclipse 0.9.107 (will update soon to 108 or whatever is
>> An error was encountered retrieving the Eclipse resource for:
>> I get this error with both the JavaSVN and JavaHL adapters.
>> The .metadata directory is ignored with svn:ignore on the parent
>> Folder. I just don't get it, since Eclipse should know about it's
>> own .metadata folder and that it isn't part of my project resources
>> in any way.
> I guess the main question is what would be triggering us to even be
> looking at that folder? Is your entire workspace folder and
> working copy? There are known problems if that is the case.
Well I'm not sure if I fully understand the question.. but I think
the answer is yes.
That is, there is a .svn folder that is a sibling of the .metadata
folder, so my "workspace" folder is a working copy from that
perspective. But I would have that this would be a very common
case. My workspace has several related projects all of which are in
subversion. I have grouped these projects in subversion so they have
a common version-controlled parent folder. I checkout that parent
folder to effectively create a space where I can make an Eclipse
workspace. The .metadata folder is NOT in subversion and is
explicitly ignored via svn:ignore as I mentioned.
What are the known problems?
What should I do instead? It seems that I'm going to have to deal
with some awkward messing around with my folder structure in
subversion... I don't want that since it is working well for me and
this particular issue doesn't appear to be causing any harm.
Hopefully the "known problems" will be resolved with changes to
Eclipse and/or Subclipse.
> ... I just have no idea what would be triggering us to be looking
> at this folder
> in the first place. We do not just go snooping around your disk. We
> respond to events we are sent by the framework.
That's what I find strange as well. Eclipse should of course know
better than to treat the .metadata folder that it created and manages
as a project resource of some sort. I will try to narrow down the
operation that triggers this message. I noticed it today as I was
trying to figure out how to use the Synchronize view. (OT: I never
use it because I find it very unintuitive... I'm never sure what
something is going to do and it always looks like it will add files
to version control that I don't want added. I'm trying to figure it
out because it looks like it might be useful if I can get past that.)
What sort of experiment might be useful to get some useful info about
this .metadata "resource" problem? So far it seems the messgae can
be safely ignored.. but it still bugs me :)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Mar 16 15:38:30 2006