Bug 426979 - Upgrade execution environment to Java6 or higher
Summary: Upgrade execution environment to Java6 or higher
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-30 05:28 EST by Xavier Coulon CLA
Modified: 2014-11-25 04:22 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Coulon CLA 2014-01-30 05:28:13 EST
Hello,

Please, can you upgrade the execution environment of the eclipse.jdt.ui projects to Java 6 ? The motivations are the same as the ones described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=421017 (same request but for jdt.core). 
Furthermore, having to install Java SE 1.4 and 5 on MacOSX is a bit of a pain. 

Thanks for your understanding.
Comment 1 Dani Megert CLA 2014-02-11 09:53:13 EST
jdt.ui is already 1.5.
Comment 2 Xavier Coulon CLA 2014-02-11 10:06:24 EST
Daniel,

Some projects are still Java 1.4:
org.eclipse.jdt.astview
org.eclipse.jdt.core.manipulation
org.eclipse.jdt.junit.core
org.eclipse.jdt.junit.runtime
org.eclipse.jdt.ui.examples.javafamily
org.eclipse.jdt.ui.examples.projects
org.eclipse.ltk.core.refactoring
org.eclipse.ltk.core.refactoring.tests
org.eclipse.ltk.ui.refactoring
org.eclipse.ltk.ui.refactoring.tests
Comment 3 Dani Megert CLA 2014-02-11 10:13:15 EST
(In reply to Xavier Coulon from comment #2)
> Daniel,
> 
> Some projects are still Java 1.4:
> org.eclipse.jdt.astview
> org.eclipse.jdt.core.manipulation
> org.eclipse.jdt.junit.core
> org.eclipse.jdt.junit.runtime
> org.eclipse.jdt.ui.examples.javafamily
> org.eclipse.jdt.ui.examples.projects
> org.eclipse.ltk.core.refactoring
> org.eclipse.ltk.core.refactoring.tests
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ltk.ui.refactoring.tests

Yes, I know about them. But we only move forward along with generifying the project and currently we don't have time to do this.
Comment 4 Xavier Coulon CLA 2014-02-11 10:18:12 EST
Daniel,

Sorry, I'm not sure I understand your last comment. My question was initially about setting the Bundle-RequiredExecutionEnvironment entry in the MANIFEST.MF to JavaSE-1.6 (or at least JavaSE-1.5 for the plugins still requiring 1.4)

I'm not talking about changing anything in the Java code, but at least this upgrade would allow future contributions to use annotations and more recent APIs.
Comment 5 Dani Megert CLA 2014-02-11 10:25:52 EST
(In reply to Xavier Coulon from comment #4)
> Daniel,
> 
> Sorry, I'm not sure I understand your last comment.

If we go beyond 1.4 we'd like avoid, i.e. not just suppress raw type warnings. This requires some work.
Comment 6 Timo Kinnunen CLA 2014-02-11 16:54:09 EST
I don't know what that's supposed to accomplish. However, I do know that after getting JDT Core, JDT UI, their tests, and all other BETA_JAVA8 projects to compile starting from an effectively blank slate, the working set where they all are currently shows 0 errors and 25179 warnings. You can imagine me giving my monitor a long meaningful look right about now, if you want.