Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 161329

Summary:

Incorrect error message when loading classes

Product:

[Eclipse Project] Equinox

Reporter:

John J. Barton <johnjbarton>

Component:

Compendium

Assignee:

equinox.compendium-inbox <equinox.compendium-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

3.2

Target Milestone:

3.3 M4

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

135885

Bug Blocks:

Attachments:

Description	Flags
debug.loader console	none

Description John J. Barton

2006-10-17 18:55:15 EDT

When I tried to load my plugin I got
Unable to create view: Plug-in com.ibm.research.Fireclipse.FireclipsePlugin was unable to load class com.ibm.research.Fireclipse.FireclipseView. 

The details said
Unable to create view: Plug-in com.ibm.research.Fireclipse.FireclipsePlugin was unable to load class com.ibm.research.Fireclipse.FireclipseView.

I worked for two hours to find that this error message was incorrect.  The correct error message is:
java.lang.UnsupportedClassVersionError: com/ibm/research/Fireclipse/FireclipsePlugin (Unsupported major.minor version 49.0)

Comment 1 John J. Barton

2006-10-17 19:08:11 EDT

Created attachment 52174 [details]
debug.loader console

I eventually found the correct error message by running my plugin with debug.loader set true and reading the console.  Both the correct error message and the incorrect message is shown on the trace.

Comment 2 Thomas Watson

2006-10-25 09:33:21 EDT

This is true.  Improvements in lazy-start proposed in bug 135885 will help here.  Using this approach we define the class before attempting to activate the bundle.  This will allow ClassFormatErrors to be propagated correctly to the client.

Comment 3 Thomas Watson

2006-11-07 13:45:31 EST

A fix has been released for 3.3 M4.

The actual fix got released with the overall lazy-start changes from bug 135885.