----- Original Message -----
From: "Sudhir Khanger" <ml(a)sudhirkhanger.com>
Sent: Friday, October 31, 2014 10:42:28 PM
Subject: [fedora-java] Eclipse Luna on Fedora 21 and JDK 8 requirement
On Fri, Oct 31, 2014 at 12:18 PM, Aleksandar Kurtakov
> Besides many technical reason the biggest one is non-technical in my eyes -
> no one volunteered to do it. You know it's always a matter of "who will do
> the work?". I'm pretty sure that if someone jumps in and say "Hey,
> maintain Java 6, fix problems/adopt Java 6 to changes in the OS if
> neeeded, help strengthen the switching between JREs, go through the Java
> projects(shipped in Fedora) and help them properly set their targets in
> build scripts so builds properly work on Java 6 and etc" there will be no
> objection to having Java 6. :)
I installed JDK 7 but Eclipse won't work with JDK 7 on F21 . Why
does it require explicitly OpenJDK 8? Can we not have it search Java
on system? On Arch Linux, packages search for java-environment or
java-environment >= 7?
The problem is not about finding the java executable but verifying that all libraries in
use do not use newer bytecode due to being compiled with the default. This was a huge pain
point when we had multiple Java versions. It sometime worked, sometime not - blame the
non-strict build scripts of various projects.
Do I have to build Eclipse myself if I want to use JDK 7?
So this bug is exactly what I speak of - batik or some of the other xml* packages does not
set target bytecode in their build script resulting in Java 8 bytecode being used when
compiled on Java 8. So you don't need to rebuild Eclipse but some of it's
dependencies to not use Java 8 bytecode. And doing this throughout the whole distribution
is the reason why supporting multiple JVMs is so expensive. If projects adopted sane build
procedures that give you reproducible builds everywhere supporting multiple JVMs
wouldn't have been that big problem from Java applications POV.
5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.
java-devel mailing list