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.

Bug 117667 - Resolve lexer/editorbridge unused autoload status
Summary: Resolve lexer/editorbridge unused autoload status
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Lexer (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Miloslav Metelka
URL:
Keywords: ARCH
Depends on:
Blocks:
 
Reported: 2007-10-03 16:37 UTC by Jesse Glick
Modified: 2007-10-04 14:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2007-10-03 16:37:01 UTC 
This module was removed since it is an unused autoload, and generally we do not ship unused autoload modules with the
IDE. The options are:

1. Remove it from the IDE distribution, and e.g. distribute it on stable AU to those who actually need it.

2. Include it in some kit. Probably undesirable since it would then normally be enabled.

3. If it must be shipped but normally disabled, it can be included in the list of special exemptions in
nbbuild/hudson/build-update-descriptor.xml#disabled.autoloads. Otherwise this change should automatically trigger a
failure in

http://deadlock.netbeans.org/hudson/job/javadoc-nbms/1059/testReport/org.netbeans.nbbuild/VerifyUpdateCenter/testAutoUpdateVisibility/
Comment 2 Miloslav Metelka 2007-10-04 00:24:39 UTC 
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?
Comment 3 Jesse Glick 2007-10-04 00:31:02 UTC 
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?
Comment 4 Petr Hrebejk 2007-10-04 14:18:16 UTC 
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