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 29197 - Root {jre.home}\classes not found
Summary: Root {jre.home}\classes not found
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: -S1S-
Hardware: PC OS/2
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-01 20:41 UTC by _ gtzabari
Modified: 2007-09-26 09:14 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 _ gtzabari 2002-12-01 20:41:28 UTC
Hi,

   This issue seems to be OS/2-specific.. For
months now I've been getting:

ANNOTATION: Root d:\java131\jre\classes does not
exist.

   alongside all the exceptions that pop up. I
would like to correct this assumption because
under OS/2, that path will _never_ exist for JDK
1.3.1.

    Can someone please track down why 'classes' is
needed and what happens if its missing?

Thanks,
Gili
Comment 1 Jesse Glick 2003-01-06 15:49:29 UTC
That "someone" will probably be you, if it is OS/2 specific, since no
one else will be able to reproduce.

Suspect some problem with the Java compiler getting a bogus classpath
entry - TBD why, or why it does not gracefully ignore it.

Probable workaround: make this (empty) directory.
Comment 2 _ gtzabari 2003-01-07 04:55:42 UTC
I'm more than willing to track down any OS/2-specific stuff on my end,
but first I need to know where in the Netbeans code this actually
comes from. Specifically, which variable is Netbeans trying to access
that it gets d:\java131\jre\classes or is this some built-in fixed
constant?
Comment 3 Svata Dedic 2003-01-07 11:35:47 UTC
Please attach the actual exception(s).
Comment 4 Svata Dedic 2003-01-14 13:24:42 UTC
Until I can see the entire stacktrace, closing as WORKSFORME.
Without that I could found only one place in Java module where this
could happen, but the error message is different (it reads "WARNING:
<root path> cannot be opened"), and the string is not reported as an
exception, rather only log to the logfile with INFORMATIONAL severity.
So your message is likely to come from some other location.