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: | Sourceless class files that cannot load should return more information in explorer than "error" where possible | ||
---|---|---|---|
Product: | java | Reporter: | _ tboudreau <tboudreau> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED FIXED | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Priority is changed to P4 (normal). Currently, the exception class is shown in a tooltip. Unless the Clazz module really parses the .class file (it uses reflection currently), common errors like a placement in an invalid package or missing superclasses/interfaces cannot be displayed reopened Fixed in dev & release 3.2. The tooltip now shows better message extracted from the Exception thrown from the VM [NB3.2.38] Verified Resolved for 3.3.x or earlier, no new info since then -> closing. |
Errors in Editor are not descriptive: > If there is an error in the editor, say from loading a jar file with a bad > class in it (My problem was that the classes where compiled using Metawerks > CodeWarrior...must do something silly with the .class files), the editor only > gives you an `x` to indicate it`s bad. It you expand the class to look at the > contents, all you get is a leaf called "Error". Not very descriptive, don`t > you think? Could we work on giving a little more information, like maybe WHY > the class is bad...purhaps it failed parsing, of maybe the JAR is corrupt. > SOMETHING. This has been sent.