Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-2347

Find Bugs internal error when run on projects

    XMLWordPrintable

Details

    • Hide

      1. Start JBDS
      2. Install Find Bugs from central (1.3) or http://findbugs.cs.umd.edu/eclipse (2.0.1)
      3. Create a simple project (e.g. dynamic project)
      4. Right-click your project in Project Explorer -> Find Bugs -> Find Bugs
      5. Search is in progress and at the end there is this error

      Show
      1. Start JBDS 2. Install Find Bugs from central (1.3) or http://findbugs.cs.umd.edu/eclipse (2.0.1) 3. Create a simple project (e.g. dynamic project) 4. Right-click your project in Project Explorer -> Find Bugs -> Find Bugs 5. Search is in progress and at the end there is this error

    Description

      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:

      An internal error occurred during: "Finding bugs in dynproj...".
Attempted to beginRule: P/dynproj, does not match outer scope rule: MutexSchedulingRule, resource: P/dynproj

      The workspace log:

      !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)

      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?)

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBDS-2284 Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2278 update JBT 4 / JBDS 6 Central to include latest 3rd party features

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: