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 223828 - NoClassDefFoundError: org/netbeans/modules/bugtracking/ui/issue/IssueTopComponent
Summary: NoClassDefFoundError: org/netbeans/modules/bugtracking/ui/issue/IssueTopCompo...
Status: RESOLVED WORKSFORME
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Issuetracking Framework (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-14 09:03 UTC by pavaneshwar
Modified: 2012-12-17 14:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 172564

Attachments
stacktrace (1.30 KB, text/plain)
2012-12-14 09:03 UTC, pavaneshwar 		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 pavaneshwar 2012-12-14 09:03:15 UTC 
This issue was reported manually by pavaneshwar.
It already has 3 duplicates 


Build: NetBeans IDE 6.9.1 (Build 201007282301)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.0-b17, Java(TM) SE Runtime Environment, 1.6.0_21-b07
OS: Windows 7

Stacktrace: 
java.lang.NoClassDefFoundError: org/netbeans/modules/bugtracking/ui/issue/IssueTopComponent
   at org.netbeans.modules.bugtracking.BugtrackingManager$ActivatedTCListener.propertyChange(BugtrackingManager.java:246)
   at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
   at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)
   at org.netbeans.core.windows.RegistryImpl.doFirePropertyChange(RegistryImpl.java:321)
   at org.netbeans.core.windows.RegistryImpl.access$100(RegistryImpl.java:69)
   at org.netbeans.core.windows.RegistryImpl$1.run(RegistryImpl.java:173)
Comment 1 pavaneshwar 2012-12-14 09:03:17 UTC 
Created attachment 129364 [details]
stacktrace
Comment 2 Jaroslav Tulach 2012-12-17 13:07:06 UTC 
Four reports from 6.9.x - I don't think there is anything wrong in the module system, rather some misconfiguration in the bugzilla module(s).
Comment 3 Tomas Stupka 2012-12-17 14:02:52 UTC 
(In reply to comment #2)
> Four reports from 6.9.x - I don't think there is anything wrong in the module
> system, rather some misconfiguration in the bugzilla module(s).
the build is 2.5 years old, and there are no similar reports like that. whatever the reason is, something went totally wrong. Also the missing class is and always was in the same module like the class from which the exception was thrown.

closing for now, but feel free to reopen in case the problem reappears and please also describe then what exactly you were doing with the bugtracking support when it happened. 

using a more current is also recommended.