This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 183563 - IllegalStateException: Method can be called only on model waiting for bg thread to populate it.
Summary: IllegalStateException: Method can be called only on model waiting for bg thre...
Status: RESOLVED DUPLICATE of bug 179979
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-06 13:22 UTC by Karol Harezlak
Modified: 2010-04-06 22:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 167630

Attachments
stacktrace (1.06 KB, text/plain)
2010-04-06 13:22 UTC, Karol Harezlak 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karol Harezlak 2010-04-06 13:22:17 UTC 
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) Client VM, 14.1-b02, Java(TM) SE Runtime Environment, 1.6.0_15-b03
OS: Linux

Stacktrace: 
java.lang.IllegalStateException: Method can be called only on model waiting for bg thread to populate it.
   at org.netbeans.modules.apisupport.project.ui.customizer.CustomizerComponentFactory$DependencyListModel.setDependencies(CustomizerComponentFactory.java:230)
   at org.netbeans.modules.apisupport.project.ui.customizer.SingleModuleProperties$2$1.run(SingleModuleProperties.java:523)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
   at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:125)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
Comment 1 Karol Harezlak 2010-04-06 13:22:22 UTC 
Created attachment 96773 [details]
stacktrace
Comment 2 Jesse Glick 2010-04-06 22:31:49 UTC 

*** This bug has been marked as a duplicate of bug 179979 ***