#135 Assertion failure when associating project in Eclipse3.2rc5
After installing Eclipse 3.2 RC5, I installed ccase-
eclipse version 1.1.1 (latest & greatest).
When I attempt to associate Clearcase with a project,
I get an "Internal error occurred" popup with the
text:
"Attempted to beginRule: R/, does not match outer
scope rule: P/myProject"
This happens no matter what project I use.
All was well with Eclipse 3.2 RC1.
Stack trace from the error log:
java.lang.IllegalArgumentException: Attempted to
beginRule: R/, does not match outer scope rule: P/OHS-
test
at org.eclipse.core.runtime.Assert.isLegal
(Assert.java:62)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush
(ThreadJob.java:116)
at org.eclipse.core.internal.jobs.ThreadJob.push
(ThreadJob.java:225)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin
(ImplicitJobs.java:58)
at org.eclipse.core.internal.jobs.JobManager.beginRule
(JobManager.java:219)
at org.eclipse.team.core.RepositoryProvider.map
(RepositoryProvider.java:95)
at
net.sourceforge.eclipseccase.ui.actions.AssociateProjec
tAction$1.run(AssociateProjectAction.java:44)
at
net.sourceforge.eclipseccase.ui.actions.ClearcaseWorksp
aceAction$1.execute(ClearcaseWorkspaceAction.java:75)
at
org.eclipse.ui.actions.WorkspaceModifyOperation$1.run
(WorkspaceModifyOperation.java:101)
at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1737)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:113)
at
org.eclipse.jface.operation.ModalContext$ModalContextTh
read.run(ModalContext.java:113)
Logged In: YES
user_id=1549926
I get the identical problem.
Regards,
Mike
Logged In: YES
user_id=372260
Roel, can you look into this? I think it's a small fix
because of a change in Eclipse regarding scheduling rules.
We run with the IProject scheduling rule but Eclipse changed
and now requires lock the whole workspace. So it should be
changed to IWorkspace#getRoot
Logged In: YES
user_id=1258114
I think the problem should not even exist. I checked this
class:
<http://eclipse-ccase.cvs.sourceforge.net/eclipse-ccase/net.sourceforge.eclipseccase.ui/src/net/sourceforge/eclipseccase/ui/actions/AssociateProjectAction.java?revision=1.5&view=markup>
and getSchedulingRule() method and it seems workspace is
locked. If i compile your feature myself i can associate CC
to my projects, and if i'm using 1.1.1 version from update
site, the problem occurs. When i commented out this method
(so super method with multi project locking has been used)
the problem also occured.
So it seems, the code is right but i don't know why
something is wrong with official 1.1.1 build.
And one thing i'm at home now, and obviously i don't have
ClearCase here, so i renamed notepad.exe to cleartool.exe.
But i think it can simulate CC enought to test project
association. ;)
Thanks for the plugin again!
Logged In: YES
user_id=372260
The update site is out of date. Open
http://eclipse-ccase.sourceforge.net/update/ in a browser
and you'll see that it's still on 1.1.0. Sorry for that.
So it's already fixed in 1.1.1