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.
Reported also as a part of issue 132662 .... Build: NetBeans IDE Dev (Build 200806180005) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06, Java(TM) SE Runtime Environment, 1.6.0_02-b06 OS: Windows XP, 5.1, x86 User comments: I downloaded the nightly buld of 18th June to see if the hangup I'd been getting when moving away from editing JSPs had been resolved. This assertion error came up the first time I openned one of the JSPs. The original problem was being handled as Issue 132662. It might be relevant that the JSP involved contains Javascript whose generation is controlled by JSTL loop and conditional tags. This throws up many error javascript syntax error markers (though the code generated into the HTML is valid). STACKTRACE: (first 10 lines) java.lang.AssertionError: tmc:scriptLiteral value=''/>"1:a at org.mozilla.javascript.TokenStream.getToken(TokenStream.java:358) at org.netbeans.modules.javascript.editing.lexer.JsLexer.nextToken(JsLexer.java:195) at org.netbeans.lib.lexer.LexerInputOperation.nextToken(LexerInputOperation.java:178) at org.netbeans.lib.lexer.JoinTokenList.init(JoinTokenList.java:104) at org.netbeans.lib.lexer.TokenListList.<init>(TokenListList.java:128) at org.netbeans.lib.lexer.TokenHierarchyOperation.tokenListList(TokenHierarchyOperation.java:408) at org.netbeans.lib.lexer.EmbeddingContainer.createEmbedding(EmbeddingContainer.java:282) at org.netbeans.api.lexer.TokenSequence.createEmbedding(TokenSequence.java:416) at org.netbeans.modules.html.editor.coloring.EmbeddingUpdater.createEmbedding(EmbeddingUpdater.java:303) at org.netbeans.modules.html.editor.coloring.EmbeddingUpdater.createEmbedding(EmbeddingUpdater.java:241)
This seems to be an issue with JavaScript editing.
Any information on how to reproduce this bug? It looks from the stacktrace like it's related to the lexer, and since it was filed in June, I suspect it was fixed. I remember there were a lot of issues around lexing in June after integration f6b2e0181e07 - 3 days before this issue was filed.
Actually, I don't think leaving the bug open makes sense, it is very likely fixed given the lexer problems we had in June and the time this was filed. If it can be reproduced on current bits, please describe how to do it.
v/c