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: | Resolve lexer/editorbridge unused autoload status | ||
---|---|---|---|
Product: | editor | Reporter: | Jesse Glick <jglick> |
Component: | Lexer | Assignee: | Miloslav Metelka <mmetelka> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | geertjan |
Priority: | P2 | Keywords: | ARCH |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jesse Glick
2007-10-03 16:37:01 UTC
Sorry, the actual failing test is here: http://deadlock.netbeans.org/hudson/job/javadoc-nbms/1062/testReport/org.netbeans.nbbuild/VerifyUpdateCenter/synchronicConsistency/ The problem was that Geertjan's ManifestLexer example in the book uses the editorbridge module but as it's not included in the IDE the building of the example on top of platform now fails. As http://openide.netbeans.org/servlets/ReadMsg?list=dev&msgNo=30651 indicates a user attempted to build a similar thing for his language. I incline to #3 if it's not a problem (btw the module is fairly small) but #1 could possibly be a satisfying solution too. Is it fine to use #3? Up to you. My mild preference would be for #1 and add a note to book errata. It is not unusual for some doc to be written on how to do something which requires some API which is pulled from the product before release. I presume the module is not terribly important in general if no one in any of the IDE teams needed it? Did #3 for now. Checking in build-update-descriptor.xml; /cvs/nbbuild/hudson/build-update-descriptor.xml,v <-- build-update-descriptor.xml new revision: 1.14; previous revision: 1.13 done |