Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [linuxtools-dev] Use of Java 6 classes break compile

On 01/15/2013 05:52 PM, Aleksandar Kurtakov wrote:
----- Original Message -----
From: "sami wagiaalla" <swagiaal@xxxxxxxxxx>
To: "Linux Tools developer discussions" <linuxtools-dev@xxxxxxxxxxx>
Sent: Tuesday, January 15, 2013 9:48:23 PM
Subject: Re: [linuxtools-dev] Use of Java 6 classes break compile

Furthermore, the JDT preference set in the plugin's
      .settings/org.eclipse.jdt.core.prefs
file is:
      org.eclipse.jdt.core.compiler.source=1.5
which explains why my system uses Java 5 to compile that plugin
although I have Java 6 installed.

How come my eclipse does not report these errors. What settings
should I
use to make sure I see errors like these.

Should the isEmpty() be removed, or do you want to move the plugin
to Java 6?  I can open a bug if you'd like

I don't see any reason not to move to 1.6
Well, Java 6 is will be EOLed next month so moving to 1.6 should be a no-brainer. We should even consider using Java 7 nowadays.

What if keep it following Eclipse Kepler target environments? -> http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#target_environments

So keep Java 6 still minimum required.

My 10 cents...


Alexander Kurtakov
Red Hat Eclipse team


_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev




Back to the top