Bug 1084097

please do NOT remove java 7 from Fedora.
java 7 is not EOL and it's used in waaaaay to many deployments.

we had this problem before when java 6 was removed...

Hi Ferry, Although Java 7 is not EOLd yet, it will be in April 2015:
http://www.oracle.com/technetwork/java/eol-135779.html

Assuming F21 is released in October per tentative plans, that means that Java 7 will be EOLd 8 months before F21 hits EOL [November 2015]. 

Not wanting to leave F21 with an insecure JDK is the primary reason for the switch to OpenJDK8.

I do appreciate that.
However, _removing_ it from Fedora denies the user the choice to install it.

Having Java 8 as the default is fine.
_not_ having Java 7 will be painful for many.
There are many (subtle) differences going from Java 7 to 8.
Removing J7 removes any transition time.

It is not as simple as just shipping it on the side unfortunately. 

Once we switch to OpenJDK8, we will begin rebuilding the Java stack with OpenJDK8 to flush out errors. As this happens, those packages will stop working with OpenJDK7/Java7 as Java 8 uses a new class file version. By the time F21 is released, a large part of the Fedora Java stack will no longer work with OpenJDK7.

you can easily avoid that by compiling for 1.7 profile and give people time to transition their packages.

And it still removes the choice.

People use Fedora with non-fedora software too, some of which is (blasphemy) not open source.

Personally, I'm involved in OSGi (bnd/bndtools) and I known this lack of transition time will give me some headaches

(In reply to Ferry Huberts from comment #3)
> Removing J7 removes any transition time.

The transition time is now: OpenJDK 8 is available in Fedora 19 and 20 as optional.

As Omair mentioned, OpenJDK8 has been in Fedora for a while.

Additionally, compiling for the 1.7 profile is non trivial given the sheer number of Java packages in Fedora (~800) and the myriad of build mechanisms they use.

A bit of gentle warning:

There are many subtle and not so subtle differences when going from J7 to J8.
The OSGi Alliance is prototyping conversion of all their builds to J8 and they're finding many issues.

There might be a non-trivial amount of fall-out from forcing J8

Just so that you'd know ;-)

(In reply to Ferry Huberts from comment #8)
> There might be a non-trivial amount of fall-out from forcing J8

At this point, we don't really have an option. OpenJDK 7 (and Java 7) are being EOL'ed in a year: http://mail.openjdk.java.net/pipermail/jdk7u-dev/2014-April/008910.html.

Should we really leave all Fedora users running a version of OpenJDK that may contain security vulnerabilities?

Release notes copy available for review at https://fedoraproject.org/wiki/Documentation_Java_Beat#Update_to_OpenJDK_8

(In reply to Pete Travis from comment #10)
> Release notes copy available for review at
> https://fedoraproject.org/wiki/Documentation_Java_Beat#Update_to_OpenJDK_8

Should I make changes to the page directly?

The link "http://openjdk.java.net/projects/jdk8/features/" doesn't work, it should be "http://openjdk.java.net/projects/jdk8/features" (no trailing slash).

Looks good otherwise. Thanks!

I've made that change, Omair, but if you think of something else, you are welcome to edit the page.

This message is a reminder that Fedora 21 Change Checkpoint: 100% Code Complete Deadline (Former Accepted Changes 100% Complete) is on 2014-10-14 [1].

All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a point of contingency plan. All incompleted Changes will be reported to FESCo on 2014-10-15 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/21/Schedule