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: | ClassNotFoundException (TraceLogger) on every startup | ||
---|---|---|---|
Product: | ide | Reporter: | _ gtzabari <gtzabari> |
Component: | Logger | Assignee: | logger-issues@ide <logger-issues> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | OS/2 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ gtzabari
2001-05-05 23:03:18 UTC
On Mon, 07 May 2001 11:25:21 -0700, Roger Blumer wrote:
>it looks like you had the logger module installed and either uninstalled it
>or moved to a new version and haven't installed the logger module into it.
>Could you let me know if that's true, and which one it is?
>I think the fix is different depending on how it occurred.
I installed Netbeans 3.2 beta.. I didn't uninstall Logger, I stuck to the
default configuration. I ran the upgrade manager, downloaded whatever patches
were available and applied them, which is exactly when the problem showed up.
That's all I know .. :)
Gili
I found out this was related to a typo in my OS/2 startup scripts. runideos2.cmd (version 1.6) fixes this. Thanks for the follow-up, Gili.
The startup script problem makes sense with what Jesse Glick saw as the problem:
> it looks like the user had the logger module installed and either
> uninstalled it or moved to a new version and hasn't installed the logger
> module into it.
>
NoClassDefFoundError, not a ClassNotFoundException (which is OK and should
only happen once and be nicely reported by projects module). Looks like
modules/logger.jar is there but not lib/ext/logger.jar.
I don't understand your last sentence, please rephrase.. What the sentence implies is that somehow lib/ext/logger.jar was not getting added to the classpath, so the modules/loggerModule.jar could not find the class it needed. Since jars in lib/ext are added to the classpath by the startup script, an error in that script could cause the problem reported. |