[jbosstools-issues] [JBoss JIRA] (JBDS-2347) Find Bugs internal error when run on projects

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724358#comment-12724358 ] 

Martin Malina commented on JBDS-2347:
-------------------------------------

Found it here:
http://sourceforge.net/tracker/index.php?func=detail&aid=3560636&group_id=96405&atid=614693
Fixed in their head. Should be fixed in 2.0.2 I believe.
                
> Find Bugs internal error when run on projects
> ---------------------------------------------
>
>                 Key: JBDS-2347
>                 URL: https://issues.jboss.org/browse/JBDS-2347
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: 3rdPartyCertification, 3rdPartyDependencies
>    Affects Versions: 6.0.0.Alpha2
>         Environment: OS X 10.8
> JBDS 6.0.0.Alpha2d
> Find Bugs 1.3, Find Bugs 2.0.1
>            Reporter: Martin Malina
>            Assignee: Nick Boldt
>             Fix For: 6.0.0.Beta1
>
>
> When you run find bugs on a project (e.g. dynamic web project or java ee web project from central), it will search for bugs and then you will get an error:
> {code}
> An internal error occurred during: "Finding bugs in dynproj...".
> Attempted to beginRule: P/dynproj, does not match outer scope rule: MutexSchedulingRule, resource: P/dynproj
> {code}
> The workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2012-10-05 14:07:48.920
> !MESSAGE An internal error occurred during: "Finding bugs in dynproj...".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to beginRule: P/dynproj, does not match outer scope rule: MutexSchedulingRule, resource: P/dynproj
> 	at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> 	at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> 	at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> 	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> 	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:286)
> 	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
> 	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2282)
> 	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2339)
> 	at de.tobject.findbugs.reporter.MarkerUtil.createMarkers(MarkerUtil.java:125)
> 	at de.tobject.findbugs.builder.FindBugsWorker.updateBugCollection(FindBugsWorker.java:383)
> 	at de.tobject.findbugs.builder.FindBugsWorker.work(FindBugsWorker.java:227)
> 	at de.tobject.findbugs.actions.FindBugsAction$StartedFromViewJob.runWithProgress(FindBugsAction.java:265)
> 	at de.tobject.findbugs.FindBugsJob.run(FindBugsJob.java:102)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> I tried the same in JBDS 5.0.1 with Find Bugs 2.0.1 and there was no error. So it looks like something has changed between JBDS 5 and 6. (Maybe just Indigo -> Juno?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira