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 258727 - Understand and interpret new JDK9 stacktrace format
Summary: Understand and interpret new JDK9 stacktrace format
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 8.2
Hardware: PC All
: P2 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords: JDK_9
Depends on:
Blocks:
 
Reported: 2016-04-08 13:28 UTC by Martin Balin
Modified: 2016-10-11 01:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Martin Balin 2016-04-08 13:28:20 UTC 
JDK9 introduced new format of stack traces which contains also modulename. It is in format: 
fully.qualified.class.name(module_name/classname.java:<line_number>
E.g.
Exception in thread "main" java.lang.NullPointerException: Test
	at org.lib2.JigsawLib2.getName(jigsawlib2/JigsawLib2.java:18)
	at modularjigsaw.ModularJigsaw.main(modularjigsaw/ModularJigsaw.java:32)

Where:
org.lib2.JigsawLib2.getName is package name, class name, method name
(jigsawlib2/JigsawLib2.java:18) is module name/java class name: line number
Comment 1 Tomas Zezula 2016-05-16 13:37:39 UTC 
Fixed jet-main 6a395bc399d6
Comment 2 Quality Engineering 2016-10-11 01:58:56 UTC 
Integrated into 'main-silver', will be available in build *201610110002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/6a395bc399d6
User: Tomas Zezula <tzezula@netbeans.org>
Log: #258727:Understand and interpret new JDK9 stacktrace format