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 107775 - Build fails running JavaHelp search database indexer
Summary: Build fails running JavaHelp search database indexer
Status: RESOLVED INVALID
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-22 09:44 UTC by Padraig Obriain
Modified: 2007-06-22 18:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Padraig Obriain 2007-06-22 09:44:44 UTC
I am running Nevada 65 and when I try to build the IDE I get errors:

[jhindexer] Running JavaHelp search database indexer...
   [repeat] java.lang.Exception: ConfigFile and/or IndexBuilder not set

I found the following blog entry which seems to describe my problem: http://blogs.sun.com/nam/

I tried the workaround, referred to in the blog, of removing the packages SUNWjhdem, SUNWjjhdev, SUNWjhjdoc and SUNWjhdoc
and I can now build the IDE.
Comment 1 Jesse Glick 2007-06-22 18:59:05 UTC
Solaris insists on not just bundling an old version of JavaHelp - which on its own is OK - but on adding this to the
$CLASSPATH for every user (or perhaps it is the JRE/lib/endorsed dir; don't have a copy installed to check). Either
clear your $CLASSPATH (resp. endorsed dir), or remove those packages, or use a fresh JDK installation, etc.

You are encouraged to send feedback to the Solaris packaging engineers requesting that they fix the JH package to not
affect any Java environments by default; this is simply poor practice, as any app which specifically _wishes_ to use the
OS' bundled copy of JavaHelp can easily do so explicitly, but unsuspecting apps should not get it without asking
(especially when it can override their own copy!). In the future JSR 277 should obsolete this class of problem.