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: NetBeans IDE Dev (Build 20150806-dc0b00cfb387) VM: Java HotSpot(TM) 64-Bit Server VM, 25.60-b07, Java(TM) SE Runtime Environment, 1.8.0_60-ea-b07 OS: Mac OS X User Comments: tstupka: no idea, just edisting Stacktrace: java.lang.NullPointerException at org.netbeans.modules.java.hints.introduce.IntroduceHint.addExpressionFixes(IntroduceHint.java:371) at org.netbeans.modules.java.hints.introduce.IntroduceHint.computeError(IntroduceHint.java:428) at org.netbeans.modules.java.hints.introduce.IntroduceHint.run(IntroduceHint.java:242) at org.netbeans.modules.java.hints.introduce.IntroduceHint.run(IntroduceHint.java:142) at org.netbeans.modules.java.source.JavaSourceAccessor$CancelableTaskWrapper.run(JavaSourceAccessor.java:298) at org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:584)
Created attachment 155193 [details] stacktrace
Created attachment 155194 [details] stacktrace Editing java code
Created attachment 155215 [details] stacktrace Editing a test file
Created attachment 155216 [details] stacktrace just somehow clicked in java editor, sorry no idea about specific details
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=218994
Created attachment 155217 [details] stacktrace Just editing a file, no big deal
The error has been there for a long time, but it had surfaced only when "Introduce Method" fix was activated. Because of some recent changes, the unhandled NPE moved to the main hint processing :-/ sorry. Should be fixed in jet-main#33e5529188d5
Integrated into 'main-silver', will be available in build *201508110002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/33e5529188d5 User: Svata Dedic <sdedic@netbeans.org> Log: #254170: do not offer introduce method if no viable targets are found
*** Bug 254258 has been marked as a duplicate of this bug. ***