[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Subclipse 1.3.15 does not allow to update a workingset on eclipse 3.4

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 13 May 2008 10:00:27 -0400

On Tue, May 13, 2008 at 3:46 AM, Gradenegger, Roland
<Roland.Gradenegger_at_tiscover.com> wrote:
> We have two Workingsets with different branches (different project-names
> too)
> of an allmost identical application.
>
> eg. one workingset is "production" and the other is "unstable"
> (I do not think that this causes the error, this is only additional
> info)
>
> When I am trying to update either the whole workingset or even only one
> project from svn,
> then the following error occours.
> (info: unst-appli and unst-ostpr are two projects of the same
> workingset)
>
>
> Environment info:
> ================
> OS: Windows XP
> Eclipse Version: 3.4.0, Build id: I20080330-1350
> SubClipse: Tag 1.3.15
> Using: JavaHL
> Protocoll: svn://
>
> StackTrace:
> ==========
> java.lang.IllegalArgumentException: Attempted to beginRule:
> P/unst-appli, does not match outer scope rule: P/unst-ostpr
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
> 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:
> 1467)
> at
> org.tigris.subversion.subclipse.core.client.OperationManager.endOperatio
> n(OperationManager.java:118)
> at
> org.tigris.subversion.subclipse.core.commands.UpdateResourcesCommand.run
> (UpdateResourcesCommand.java:83)
> at
> org.tigris.subversion.subclipse.ui.operations.UpdateOperation.execute(Up
> dateOperation.java:73)
> at
> org.tigris.subversion.subclipse.ui.operations.RepositoryProviderOperatio
> n.execute(RepositoryProviderOperation.java:71)
> at
> org.tigris.subversion.subclipse.ui.operations.SVNOperation.run(SVNOperat
> ion.java:89)
> at
> org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableC
> ontext.java:144)
> at
> org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runI
> nWorkspace(JobRunnableContext.java:72)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWor
> kspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Thanks, I will open an issue. Eclipse 3.4 changed the scope of the
scheduling rule for a project so we have to review all places where we
made assumptions on the previous scope and fix them.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-13 16:00:45 CEST

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