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

Bug 316528

Summary: Fix J2SE 1.6 dependencies in EDC
Product: [Tools] CDT Reporter: Ed Swartz <ed.swartz>
Component: cdt-debug-edcAssignee: Ken Ryall <ken.ryall>
Status: CLOSED INVALID QA Contact: Ken Ryall <ken.ryall>
Severity: normal    
Priority: P3 CC: john.cortell
Version: 7.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
the patch none

Description Ed Swartz CLA 2010-06-10 16:23:00 EDT 
Some commits from last week introduced J2SE 1.6 dependencies in the org.eclipse.cdt.debug.edc plugin which advertises it is compatible with J2SE 1.5, which I didn't see because my system only had J2SE 1.6 installed.  This means that EDC will fail to load executables on those systems due to runtime class loading failures.

Fortunately there is only one class and one plugin affected.
Comment 1 Ed Swartz CLA 2010-06-10 16:23:22 EDT 
Created attachment 171671 [details]
the patch
Comment 2 John Cortell CLA 2010-06-10 16:27:02 EDT 
(In reply to comment #0)
> Some commits from last week introduced J2SE 1.6 dependencies in the
> org.eclipse.cdt.debug.edc plugin which advertises it is compatible with J2SE
> 1.5, which I didn't see because my system only had J2SE 1.6 installed.  This
> means that EDC will fail to load executables on those systems due to runtime
> class loading failures.
> 
> Fortunately there is only one class and one plugin affected.

I believe we have Monday as the absolute cut-off for delivering the build to eclipse.org. Are you going to call for a re-spin or hope a more important reason pops up before then? :-)
Comment 3 Ed Swartz CLA 2010-06-10 16:30:25 EDT 
I was wondering that too.  Doug said the last "do it yourself" respin chance was yesterday.  I was going to post to cdt-dev and ask.  

AFAIK, if this error didn't break the build, then there's a workaround at runtime (i.e. have JDK 6 available), but it won't be obvious what's wrong to the end user at all.
Comment 4 Ed Swartz CLA 2010-06-10 16:35:52 EDT 
Oops!  Ignore this.  The offending code was not even committed to CDT HEAD yet (it's related to bug 315420) but is only here in Austin.  Sorry for any panic this caused.