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 200711141200) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b05 OS: Linux, 2.6.22.5-31-default, i386 User Comments:
I can reproduce it too - just press enter in XML file.
It's quite serious, XML file cannot be edited -> P2
I can't edit .cpp files
*** Issue 121908 has been marked as a duplicate of this issue. ***
Not in 6.0.
Build: NetBeans IDE Dev (Build 20071115111332) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b02 OS: Windows XP, 5.1, x86 User Comments: To reproduce: - create a web application with Struts framework - open New file wizard - choose Struts|Struts Action - type a package name and action path in text fields - click Finish and the exception is thrown
Created attachment 53043 [details] stacktrace
It is a regression since build 200711131810. Last time it worked in build 200711131522.
I'm working on it.
Build: NetBeans IDE Dev (Build 071114) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Linux, 2.6.22-14-generic, i386 User Comments: Just typed some text at the end of a plain text file.
Created attachment 53069 [details] stacktrace
Thrown when simply editing a plain text file. Definitely P1.
Build: NetBeans IDE Dev (Build 200711150000) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06 OS: Windows Vista, 6.0, x86 User Comments: I opened new-created properties file.
Created attachment 53074 [details] stacktrace
I have eliminated the NPE: Checking in TokenHierarchyOperation.java; /cvs/lexer/src/org/netbeans/lib/lexer/TokenHierarchyOperation.java,v <-- TokenHierarchyOperation.java new revision: 1.32; previous revision: 1.31 but I'm still searching why the XML language is not initialized. The code in XMLKit that does doc.putProperty(Language.class, XMLTokenId.language()); does not triggered (J2EE_LEXER_COLORING is false) and the XML Lexer module does seem to have a xml layer. I did not find any place where the XMLTokenId.language() would get registered yet. I've made a small patch that bypasses the cache of LanguageManager but it still has no effect due to the missing language.
*** Issue 122077 has been marked as a duplicate of this issue. ***
*** Issue 122031 has been marked as a duplicate of this issue. ***
*** Issue 121970 has been marked as a duplicate of this issue. ***
Since the xml uses the old way of syntax highlighting I had to do one more fix in HLFactory to use it since token hierarchy is now always non-null. I have also improved TH use in SyntaxHighlighting. Checking in src/org/netbeans/modules/editor/impl/highlighting/HLFactory.java; /cvs/editor/src/org/netbeans/modules/editor/impl/highlighting/HLFactory.java,v <-- HLFactory.java new revision: 1.7; previous revision: 1.6 done Checking in lib2/src/org/netbeans/modules/editor/lib2/highlighting/SyntaxHighlighting.java; /cvs/editor/lib2/src/org/netbeans/modules/editor/lib2/highlighting/SyntaxHighlighting.java,v <-- SyntaxHighlighting.java new revision: 1.19; previous revision: 1.18 This should not appear in 6.0 since this regression was caused by issue 121829.
*** Issue 122138 has been marked as a duplicate of this issue. ***