Re: [Subclipse-users] Internal error when updating a project

On 10/07/2008 15:49 Mark Phippard ha scritto:

> There are a number of people that have been reporting this since some
> of the late 3.4 milestone releases. We have not been able to recreate
> it. So we still need to find the magic ingredient that triggers this
> so that we can figure out the fix.

I get this error regularly:

Something I can say about my workspace:

Seems that the error is independent from the project that is actually
updated (because the error is always the same), but also the name
reported in the error is also the first project in the list.

The error is related to a plugin project with an associated feature,
both sharing the same id but, of course, different project and folder
names. My first tought was that for some reasons the feature id is used
to lock the resources, instead of the project (or folder) name.

The workspace itself was checked out from svn (I have a .svn in the root
of the workspace).

The workspace and the projects were created with Eclipse 3.3, I have not
tried to create a new workspace with Eclipse 3.4 and import the projects
since this error is not blocking in my case and I have many custom
settings there.

Let me know if and how I can help.

Regards,
Marco.

-- 
Marco Maccaferri
Software Consulting, Design and Development
http://www.maccasoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org