[linuxtools-dev] Use of Java 6 classes break compile
Hi, I'm trying to compile some of the Linux Tools plugins and I'm getting three errors in the SystemTap plugins because it uses String.isEmpty() (added in Java 6), when the plugin specifies a minimum java environment of Java 5. 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. 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 Thanks Marc ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
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 ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Use of Java 6 classes break compile
- Original Message - From: sami wagiaalla swagi...@redhat.com To: Linux Tools developer discussions linuxtools-dev@eclipse.org 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. Alexander Kurtakov Red Hat Eclipse team ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
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 swagi...@redhat.com To: Linux Tools developer discussions linuxtools-dev@eclipse.org 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@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Use of Java 6 classes break compile
- Original Message - From: Wainer Moschetta waine...@linux.vnet.ibm.com To: linuxtools-dev@eclipse.org Sent: Tuesday, January 15, 2013 10:01:45 PM Subject: 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 swagi...@redhat.com To: Linux Tools developer discussions linuxtools-dev@eclipse.org 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... Just for everyone's knowledge: What you refer to is the supported environments for the Eclipse Platform project. We have the same for Linux Tools http://www.eclipse.org/projects/project-plan.php?projectid=tools.linuxtools#target_environments which clearly says we require Java 6 or newer. This is not an excuse for not having correct BREEs in bundles though. The BREE specifies what the bundle needs as minimum, while the target environment in the project plan specifies what is the minimum requirement for the project as a whole. Alexander Kurtakov Red Hat Eclipse Team ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Use of Java 6 classes break compile
-Original Message- From: linuxtools-dev-boun...@eclipse.org [mailto:linuxtools-dev-boun...@eclipse.org] On Behalf Of sami wagiaalla Sent: Tuesday, January 15, 2013 2:48 PM To: Linux Tools developer discussions 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. I'm not sure. Maybe it is because you don't have a JRE for Java 5 installed for Eclipse, so it defaults to what you have installed? In my case I have both Java 5 and 6, so it picked the one the preference settings file told it too. That's my guess anyway. Marc ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Use of Java 6 classes break compile
Yeah, I'm pretty sure it doesn't know what was added when and your Java 7 JDK is masquerading as JDK 5 here. To take full advantage of API tools one really needs actual copies of older JDKs AFAIK. Andrew On 15 Jan 2013 15:22, Marc Khouzam marc.khou...@ericsson.com wrote: -Original Message- From: linuxtools-dev-boun...@eclipse.org [mailto:linuxtools-dev-boun...@eclipse.org] On Behalf Of sami wagiaalla Sent: Tuesday, January 15, 2013 2:48 PM To: Linux Tools developer discussions 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. I'm not sure. Maybe it is because you don't have a JRE for Java 5 installed for Eclipse, so it defaults to what you have installed? In my case I have both Java 5 and 6, so it picked the one the preference settings file told it too. That's my guess anyway. Marc ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] The Validation Failed on Trace Import
All: I am doing the linux kernel tracing with LTTng 2.0 on my target hardware board. By using babeltrace tool to the trace output path, I can get the readable text on the stdout. So it proves the trace output files should be correct. However, while I installed the Eclipse Juno service pack 1 on my windows OS and then created the trace project, the Validation Failed error always show up whenever I selected the Kernel trace or generic CTF trace in Trace Import - Trace Type page. By the way, I give the same trace path in Source directory input as the one for Babeltrace. I can not find out any more additional error information to help me figure the failure reasons out. Any clues on this error? Thanks a lot on your help! Jun ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
