Community
Participate
Working Groups
MA (02.10.2001 11:21:41) Couldn't the error messages / stack traces coming from failed plugin loading be a bit more helpful? The most common stack trace is 'application not found'. and stands for all kind of problems, xml parsing error, required plugins of the application class not found, -dev bin not set... You need to enable the debug traces, to have a chance to see the problem. When 'org.eclipse.core.runtime' is not existing, the stacktrace is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException at org.eclipse.core.internal.runtime.InternalPlatform.activateDefaultPlugins(InternalPlatform.java:100) at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(InternalPlatform.java:530) Debugging the plugin classloader is a really painful experience. NOTES: JohnA (10/5/2001 12:40:17 PM) A couple of examples of bad (or misleading) error reporting: - create two plugins with circular dependency --> no error message at all, plugins aren't loaded - runtime exception in Plugin class constructor or startup() method, gets reported as a NoClassDefFoundError on the class that triggered the plugin activation.
PRODUCT VERSION: 202
From Jeff McAffer: Areas to cover: - plugin parsing - resolution - activation - creation of executable extensions
For build 20020312. Plugin related error messages are improving. Now, plugin parsing and resolving should give meaningful error messages in most error conditions. Next areas to work on are plugin activation and creation of executable extensions (see comments from Jeff McAffer).
Consider for F1. Part of servicability work.
Moving to Equinox. Covers general improvement for runtime related functions (as listed in comment 2).
Rafael did a pass on many of the error messages and we are continuously improving any additional ones as we see them. Closing.
