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

Bug 271835

Summary: Verify all BREEs are set correctly to JVM 1.4
Product: [Tools] GEF Reporter: Nick Boldt <nboldt>
Component: RelEngAssignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse, aniefer, kim.moir
Version: unspecified   
Target Milestone: 3.5.0 (Galileo) M7   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Nick Boldt CLA 2009-04-09 14:54:57 EDT
(from bug 265704 comment 7)

> p.s. I personally think we are way past the point of it being a 
> sane position to support Java 1.4.

If that's the case, and all the BREEs in GEF's manifest.mf files are set correctly to 1.4, then I can stop worrying about things like bug 271553 and start running GEF w/ JVM 5.0.

Please close this when you are satisifed that GEF can be run on 5.0 and still be 1.4 compliant.
Comment 1 Nick Boldt CLA 2009-04-09 14:57:26 EDT
I should qualify that "running GEF w/ JVM 5.0" and "run on 5.0" means "run the *build* using a 5.0 JVM". I'm not talking about end-user runtime.
Comment 2 Andrew Niefer CLA 2009-04-09 15:36:15 EDT
If all bundles specify BREEs, and the builder defines the appropriate properties for each needed environment (ie the J2SE-1.4, J2SE-1.5, JavaSE-1.6, etc) which point to appropriate class libraries to compile against for each environment;  Then the build itself can run on whatever vm you wish and each bundle is compiled independently against the proper libraries.  (This has been around since 3.3 I think).
Comment 3 Anthony Hunter CLA 2009-04-13 13:47:09 EDT
All GEF projects have:
Bundle-RequiredExecutionEnvironment: J2SE-1.4

I added this to org.eclipse.draw2d.doc.isv and org.eclipse.gef.doc.isv, which were the only two missing.