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 53440 - "Could not find java.lang in bootclasspath" message lacks important diagnostic info
Summary: "Could not find java.lang in bootclasspath" message lacks important diagnosti...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-14 19:23 UTC by Jesse Glick
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack trace (1.47 KB, text/plain)
2005-01-14 19:24 UTC, Jesse Glick 		Details
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 2005-01-14 19:23:49 UTC 
050103 custom, JDK 1.6.0 b17. I had selected
openProjectFiles(Project) from ProjectUtilities
(projects/projectui) and chosen Find Usages.
Nothing visible happened. Saw some exceptions in
console. Not clear what is wrong; have not seen
such an error before.
Comment 1 Jesse Glick 2005-01-14 19:24:17 UTC 
Created attachment 19701 [details]
Stack trace
Comment 2 Martin Matula 2005-01-17 09:41:30 UTC 

*** This issue has been marked as a duplicate of 48672 ***
Comment 3 Martin Matula 2005-01-21 09:49:01 UTC 
Reopening, changing summary, P3->P2, see Jesses justification for
making it a P2 in issue 48672.
Jesse, please provide more info. Does it happen randomly? Does
cleaning of storage files help? How often do you see this? Does it
happen on various classes?
The FatalError from the compiler does not seem to be related but the
cause of the error can be related to the cause of the malfunctioning
find usages feature.
Comment 4 Martin Matula 2005-01-21 10:04:24 UTC 
I tried to reproduce it in the current build with exactly the same
version of JDK on Fedora Core 3. I opened project/projectui and all
required, opened ProjectUtilities, right-clicked on
openProjectFiles(Project) in the editor and executed find usages. It
seemed to work fine.
Comment 5 Jesse Glick 2005-01-22 21:08:22 UTC 
Same on 1.6.0 b19, still on FC3, using a dev build (050118 custom).
Cleaning $userdir/var/cache/ and restarting does not help.

Major correction: the Usages/Refactor window *does* appear. It was
just invisible due to some window system bug; starts with zero height!
But I still see the bootclasspath error in the log file.

More new info: I still have a JDK 1.4.2_04 platform configured, but I
have deleted that JDK (in favor of 1.4.2_06). So the platform config
is wrong. apisupport/project will then be reporting an invalid
bootclasspath. So that is my problem - but why couldn't the error
message in console tip me off about this, say by listing the
bootclasspath it is trying to use which isn't working?

Sorry for not tracking this down better before. So now I think the
only problem in javacore is poor error recovery.
Comment 6 Jan Becicka 2006-10-26 16:28:16 UTC 
Javacore module was replaced by Retouche infrastructure. This bug is not valid
in trunk any more.
Comment 7 Quality Engineering 2007-09-20 12:06:15 UTC 
Reorganization of java component