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.
[ BUILD # : 200807170007 ] [ JDK VERSION : 1.6.0_07 ] I have a free-form web project. When I get a test result failure I don't now get the stacktrace in the test results window (only the output window). However, the IDe seems to detect the stack okay as when I double click on the test it jumps straight to the failed assertion.
The issue seems to be a bit more subtle than described. I have just had a test that generated a NullPointerException and that stack-trace did appear in the JUnit test results window.
And now it's missing again evne though this time it is the every same exception. Threading issue?
This is most probably caused by a bug of the nodes subsystem caused by the recent performance improvements. I will ask about the status of the respective bug and add more information here then.
The bug in nodes is bug #140866. It is marked as fixed since 2008-07-22 08:56:59 GMT. Could you please check whether it works now (in some recent build)?
It it was really caused by bug #140866 (I assume so), the stack-traces should not be missing in the last four or five daily builds. Could you please verify it?
Marked as a duplicate of bug #140866 ("Project children nodes vanish"). If you experience this bug in NB 6.5 Beta or in any development build from August or later, please reopen this. *** This issue has been marked as a duplicate of 140866 ***
Product Version: NetBeans IDE 6.5 RC1 (Build 200810171318) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b15 System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb) Verified on RC1