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 137647 - NullPointerException at org.netbeans.modules.junit.output.TroubleParser.fixateStackTrace
Summary: NullPointerException at org.netbeans.modules.junit.output.TroubleParser.fixat...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: junit-issues@java
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks: 89008
  Show dependency tree
 
Reported: 2008-06-18 23:55 UTC by dfa
Modified: 2009-03-06 15:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 66993

Attachments
stacktrace (2.24 KB, text/plain)
2008-06-18 23:55 UTC, dfa 		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 dfa 2008-06-18 23:55:42 UTC 
Build: NetBeans IDE 6.1 (Build 200804211638)
VM: Java HotSpot(TM) 64-Bit Server VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12
OS: Linux, 2.6.25-gentoo-r1-dfa, amd64

User Comments:
Comment 1 dfa 2008-06-18 23:55:46 UTC 
Created attachment 63046 [details]
stacktrace
Comment 2 Marian Petras 2008-09-05 03:11:52 UTC 
This was in a Maven project. It seems that Maven project testing produces output that cannot be parsed by the JUnit test
output parser. I will discuss this issue with the developer of Maven projects support in NetBeans.
Comment 3 cms 2008-12-03 07:10:06 UTC 
The most common way to fix this problem is to propagate the proper SPI to let project types interested in unit testing 
customize test results display. This _might_ be implemented in 7.0 but most probably this API will be added after 7.0 
release. I'll think about some temporary workaround to prevent the exception.
Comment 4 Andrey Yamkovoy 2009-03-06 15:07:23 UTC 
JUnit was switched to use Common Runner API to display results. Also code which parse Ant events was rewrote.
Now I can't reproduce this issue, so mark it as fixed. 
Could you please re-check this on the latest trunk build and reopen this issue if it's still reproducible for you?