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 20140714-7c5dac89e5c8) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Mac OS X User Comments: dstrupl: Creating new JavaFX project with FXML file. Stacktrace: java.lang.NullPointerException at org.netbeans.modules.java.editor.fold.ParsingFoldSupport$FM.invalidate(ParsingFoldSupport.java:489) at org.netbeans.modules.java.editor.fold.ParsingFoldSupport$FM.insertUpdate(ParsingFoldSupport.java:498) at org.netbeans.modules.editor.fold.FoldOperationImpl.insertUpdate(FoldOperationImpl.java:243) at org.netbeans.modules.editor.fold.FoldHierarchyExecution.insertUpdate(FoldHierarchyExecution.java:983) at org.netbeans.lib.editor.util.swing.PriorityDocumentListenerList.insertUpdate(PriorityDocumentListenerList.java:85) at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:202)
Created attachment 148032 [details] stacktrace
Fixed in jet-main#6bd39f3727f1
The exception is still reproducible on: Product Version: NetBeans IDE Dev (Build 201407250001) Java: 1.7.0_55; OpenJDK 64-Bit Server VM 24.51-b03 Runtime: OpenJDK Runtime Environment 1.7.0_55-b14 System: Linux version 3.13.0-32-generic running on amd64; UTF-8; de_DE (nb) See: http://statistics.netbeans.org/analytics/exception.do?id=731731
Created attachment 148335 [details] stacktrace Opened a project.
Evaluate Expression window is unusable due to this bug. This affects debugging.
Created attachment 148336 [details] stacktrace Just started netbeans
(In reply to ulfzibis from comment #3) > The exception is still reproducible on: > > Product Version: NetBeans IDE Dev (Build 201407250001) > Java: 1.7.0_55; OpenJDK 64-Bit Server VM 24.51-b03 > Runtime: OpenJDK Runtime Environment 1.7.0_55-b14 > System: Linux version 3.13.0-32-generic running on amd64; UTF-8; de_DE (nb) > > See: > http://statistics.netbeans.org/analytics/exception.do?id=731731 Please note that the automaton doing merge into main-silver *did not* yet noted the changeset is merged. Unless you run your custom build compiled from jet-main repository sources, build 201407250001 simply cannot have this defect fixed as it did not propagate (yet).
(In reply to Svata Dedic from comment #7) > Please note that the automaton doing merge into main-silver *did not* yet > noted the changeset is merged. Unless you run your custom build compiled > from jet-main repository sources, build 201407250001 simply cannot have this > defect fixed as it did not propagate (yet). I'm member of NetCAT and we were instructed to use nightly builds for 8.01 testing. So I was thinking, bug fixes will go to nightly builds automatically. Do I understand correct, that fixes to jet-main are not merged to nightly builds but from main-silver? Do I have to wait for integration in main-silver to continue 8.01 testing, current build 201407250001 is not usable for me because resolving hg conflict is essentially to me?
*** Bug 245841 has been marked as a duplicate of this bug. ***
AFAIK yes, we need to wait for the integration to main repo since the nightly builds are made from there. Looks like jet-main repo is unstable (http://deadlock.netbeans.org/job/jet-main/) and probably this is why it was not integrated yet.
Not in 8.0 builds.
Integrated into 'main-silver', will be available in build *201407300001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/6bd39f3727f1 User: Svata Dedic <sdedic@netbeans.org> Log: #245642: ignore files without source in parser-based fold manager
v. Build 20140730-2f4b323bfe57