Bug 171799 - Eclipse doesn't start properly on top of a JDK7b06 VM
Summary: Eclipse doesn't start properly on top of a JDK7b06 VM
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M1   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-26 09:51 EST by Olivier Thomann CLA
Modified: 2007-01-26 22:27 EST (History)
3 users (show)

See Also:

Attachments
Log file (7.66 KB, text/plain)
2007-01-26 09:52 EST, Olivier Thomann CLA 		no flags Details
Profile defined by Pascal (3.71 KB, text/plain)
2007-01-26 09:52 EST, Olivier Thomann CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2007-01-26 09:51:01 EST 
When trying to run Eclipse 3.2.1 recompiled in 1.6 target (see bug 169017 and bug 171472), using a JDK7b06 VM, it failed almost immediately.
I'll attach the log.
The reason of the failure is the missing J2SE-17 profile in the plugin org.eclipse.osgi.
Pascal added it based on the 1.6 profile and I could then successfully start Eclipse.
Comment 1 Olivier Thomann CLA 2007-01-26 09:52:14 EST 
Created attachment 57595 [details]
Log file

The log of the failure.
This error should be reported more nicely and we might implement a fallback mecanism. When a profile is missing, we could revert to a "default" profile.
Comment 2 Olivier Thomann CLA 2007-01-26 09:52:51 EST 
Created attachment 57596 [details]
Profile defined by Pascal

Once this file is added to org.eclipse.osgi_3.2.1.R32x_v20060919.jar. I can start Eclipse.
Comment 3 Thomas Watson CLA 2007-01-26 18:08:01 EST 
In the 3.3 release we default back to the highest compabible profile if the there is not one available that matches the EE we are running on.  In this case we would fall back to the JavaSE-1.6 profile.

We have also improved the error message and handling in 3.3 for this case.  The error was occuring because we did not fall back to a profile and did not set any value for the EE.  This caused the system bundle to not be resolved because it states it needs the OSGi/Minimum-1.0 EE.  We now properly fall back to the next best profile.  If all else fails we at least set the EE to OSGi/Minimum-1.0 so that the system bundle is allowed to resolve.
Comment 4 Olivier Thomann CLA 2007-01-26 22:27:21 EST 
If adding the attached profile fixes the case for 3.2.x build, you might want to add it for 3.2.2.