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.
There seems to be a glitch in the editor when editing interfaces. Some comments when added cause the editor to think there is a parse error. It displays the red xed circle icon badge and says there is an error when the class is drilled down in the explorer. These classes compile fine, and when the comments are removed, the interfaces parse as expected. // comments commenting out a line cause problems. There may be more.
I tried to reproduce it, but was not succesfull (only small attempt). But, it would be really usefull to attach an example interface to the bug. I think this is problem of java parser, which is not part of editor.
If you are sure that a specific text caused the error, please send us the text and mark the portion that confused the parser. Also please look in your ide.log file - some exception or message from the parser may be logged there.
This error seems to crop up only when there are references to other classes which sometimes the parserDB balks at due to the size of my project. This parserDB problem was issue #10955 and marked as a duplicate of 8295. I'd really like 8295 fixed. From what I can tell. I can reproduce the error by: 1) Edit file. (comment out a line) 2) Compile file. (compiles ok) 3) Put line back. 4) Compile again. (compiles ok) 5) Error... The file compiles ok, and then the "needs compile" icon badge is replaced by the error badge. I'm unable to send the actual file due to concerns by my company, however included below is the error sent to the ide.log file when this problem occurs. I can get the error badge to go away if I make a token change and then recompile the file. java.lang.NullPointerException at org.netbeans.modules.java.codesync.SourceConnectionSupport.getDependencies(SourceConne ctionSupport.java:483) at org.netbeans.modules.java.codesync.SourceConnectionSupport.splitNewMethods(SourceConne ctionSupport.java:733) at org.netbeans.modules.java.codesync.SourceConnectionSupport.notify(SourceConnectionSupp ort.java:648) at org.openide.loaders.ConnectionSupport.fireEvent(ConnectionSupport.java:246) at org.netbeans.modules.java.codesync.ModelEventAdapter.changesCommited(ModelEventAdapter .java:288) at org.netbeans.modules.java.model.DefaultLangModel.fireCommitEvents(DefaultLangModel.jav a:417) at org.netbeans.modules.java.model.DefaultLangModel.firePostCommitEvents(DefaultLangModel .java:386) at org.netbeans.modules.java.model.DefaultLangModel.processOutputQueue(DefaultLangModel.j ava:372) at org.netbeans.modules.java.model.DefaultLangModel.releaseWriteLock(DefaultLangModel.jav a:338) at org.netbeans.modules.java.model.DefaultLangModel.runUpdate(DefaultLangModel.java:487) at org.netbeans.modules.java.parser.ParsingSupport$Processor.parseLockModel(ParsingSuppor t.java:600) at org.netbeans.modules.java.parser.ParsingSupport$Processor.run(ParsingSupport.java:535) at org.openide.util.Task.run(Task.java:124) at org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:622)
OK, the stacktrace pointed to a problem: lazy (too lazy) initialization Fixed in release 3.2 & trunk.
Target milestone -> 3.2
Resolved for 3.4.x or earlier, no new info since then -> closing.
Hello guys this is a awesome place and nice post i found a lot of informative information here http://dvdplayerwindows10.com is a beast quality and latest version i sure like it.