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.
Summary: | Lexer module cannot be built incrementally under JDK 5 | ||
---|---|---|---|
Product: | editor | Reporter: | Jesse Glick <jglick> |
Component: | Lexer | Assignee: | issues@editor <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | JDK_SPECIFIC, REGRESSION |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jesse Glick
2007-11-06 07:31:02 UTC
Caused, I guess, by mmetelka's recent changes in the Lexer API. Apologies. Checking in TokenHierarchyOperation.java; /cvs/lexer/src/org/netbeans/lib/lexer/TokenHierarchyOperation.java,v <-- TokenHierarchyOperation.java new revision: 1.30; previous revision: 1.29 Thanks, workaround looks reasonable. Not sure whether this should be merged to release60. Unlikely to affect official builds, which should be clean builds, but could possibly affect developers working on that branch in the future. A simpler fix (just a variable for Language<?> is enough): Checking in TokenHierarchyOperation.java; /cvs/lexer/src/org/netbeans/lib/lexer/TokenHierarchyOperation.java,v <-- TokenHierarchyOperation.java new revision: 1.31; previous revision: 1.30 I will integrate to release60 too. I would like to integrate the latest fix into release60 to prevent possible build failures. There is NO change in functionality so it should not cause any regression. Fix looks safe to me. Integrated in release60: Checking in src/org/netbeans/lib/lexer/TokenHierarchyOperation.java; /cvs/lexer/src/org/netbeans/lib/lexer/TokenHierarchyOperation.java,v <-- TokenHierarchyOperation.java new revision: 1.29.2.1; previous revision: 1.29 v/c |