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

On 10/07/2008 19:22 Hale,Katherine ha scritto:

> You might try writing down very specific steps (step 1 do this, step 2
> do this), ideally with a public repository, so developers could attempt
> to reproduce it. Can you also dig up the stack trace from your .log
> file? Within your workspace, it should be under the .metadata
> directory.

The steps to reproduce are quite simple: right-click on a project,
select Team -> Update.

In my previous message I stated that the error was always the same, I
was wrong, the error changes, here is a stack trace:

java.lang.IllegalArgumentException: Attempted to beginRule:
P/com.tictactec.ta.lib, does not match outer scope rule:
P/org.eclipsetrader.core
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:122)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:232)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:58)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:230)
at
org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:117)
at
org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1747)
at
org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1470)
at
org.tigris.subversion.subclipse.core.client.OperationManager.endOperation(OperationManager.java:119)
at
org.tigris.subversion.subclipse.core.commands.UpdateResourcesCommand.run(UpdateResourcesCommand.java:83)
at
org.tigris.subversion.subclipse.ui.operations.UpdateOperation.execute(UpdateOperation.java:73)
at
org.tigris.subversion.subclipse.ui.operations.RepositoryProviderOperation.execute(RepositoryProviderOperation.java:71)
at
org.tigris.subversion.subclipse.ui.operations.SVNOperation.run(SVNOperation.java:89)
at
org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableContext.java:144)
at
org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runInWorkspace(JobRunnableContext.java:72)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

In that case, com.tictactec.ta.lib is the first project visible from
project explorer and *not* affected by the update,
org.eclipsetrader.core is the project that was updated. In my
understanding of the resource locking mechanism, it seems that you are
correctly locking the updated resource, but for some reasons you also do
something on an unrelated resource. A quick fix may be to lock the
workspace root instead of the project.

If you want to try with my repository, feel free to check-out the
projects from:

http://svn.eclipsetrader.org/svnroot/eclipsetrader

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