Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 268429 - NullPointerException at
NullPointerException at
Product: java
Classification: Unclassified
Component: Compiler
All All
: P2 with 1 vote (vote)
: Dev
Assigned To: Dusan Balek
Depends on:
  Show dependency treegraph
Reported: 2016-10-09 16:22 UTC by mosca_morta
Modified: 2017-05-27 03:32 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT

stacktrace (6.14 KB, text/plain)
2016-10-09 16:22 UTC, mosca_morta
stacktrace (6.16 KB, text/plain)
2016-11-28 21:09 UTC, Jesse Glick
stacktrace (6.16 KB, text/plain)
2016-12-05 17:24 UTC, Jesse Glick
stacktrace (6.21 KB, text/plain)
2016-12-13 16:15 UTC, ytn01

Note You need to log in before you can comment on or make changes to this bug.
Description mosca_morta 2016-10-09 16:22:40 UTC
This bug was originally marked as duplicate of bug 246934, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.2 (Build 201609300101)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.101-b13, Java(TM) SE Runtime Environment, 1.8.0_101-b13
OS: Mac OS X

User Comments:
mosca_morta: .

Comment 1 mosca_morta 2016-10-09 16:22:41 UTC
Created attachment 162408 [details]
Comment 2 Jesse Glick 2016-11-28 21:09:05 UTC
Created attachment 163061 [details]

Scanning Jenkins core sources.
Comment 3 Jesse Glick 2016-11-28 21:21:59 UTC
Trying to figure out if this is the bug which is causing the IDE to become barely usable for running tests in CoS mode: every time I try to do so, I get an error about some class missing a code attribute on a method. I think this is due to broken classpath scanning. Running a Maven clean build does not help, because cleaning generated sources triggers new IDE scanning that I cannot suppress, which overwrites valid class files with junk. Closing the project(s) and then running a clean build from an external shell allows me to use the right class files, but then makes the CoS part not work at all.
Comment 4 Jesse Glick 2016-12-05 17:24:07 UTC
Created attachment 163155 [details]

Classpath scanning.
Comment 5 Jesse Glick 2016-12-08 23:03:11 UTC
Does seem to be associated with broken CoS testing. Makes dev builds unsuitable for working on Jenkins core.
Comment 6 Jesse Glick 2016-12-09 18:10:12 UTC
Tried deleting my cache. Now I do not seem to get this; I get #200970 instead. I suppose that is an improvement.
Comment 7 Jesse Glick 2016-12-12 13:53:35 UTC
Got this again even after having deleted my cache recently, so it is not attributable merely to having ancient and broken class files lying around.

BTW the code triggering this seems to be

interface OpMatcher {
    boolean matches(String op);
    OpMatcher ALL = new OpMatcher() {
        public boolean matches(String op) {
            return true;
Comment 8 ytn01 2016-12-13 16:15:47 UTC
Created attachment 163224 [details]

Installed IDE and launched it,
IDE asked to set master password ( I entered one)
IDE opened projects from last session (some java, maven, platform and web)
IDE started indexing maven repository

Then exception popped
Comment 9 Jesse Glick 2017-02-21 16:05:06 UTC
Last I checked this was consistently reproducible just by checking out and opening all the modules.
Comment 10 Exceptions Reporter 2017-05-12 12:37:18 UTC
This bug already has 20 duplicates 
Comment 12 Quality Engineering 2017-05-27 03:32:35 UTC
Integrated into 'main-silver', will be available in build *201705270001* on (upload may still be in progress)

User: Dusan Balek <>
Log: Issues #270696, #268429, #200970, and #257649 fixed.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo