<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved-->

+

* email: dbhole at redhat dot com

+

+

== Current status ==

+

+

* Targeted release: [[Releases/17 | Fedora 17]]

+

* Last Updated: 2012-03-15

+

* Percentage of completion: 100%

+

+

== Detailed Description ==

+

<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->

+

OpenJDK7 has been available as a tech preview in Fedora 16 since GA.

+

+

In Fedora 16, the default JDK has been kept as OpenJDK6 due to the relative untested state of OpenJDK7 at the time. OpenJDK7 has received a fair bit of testing since in Fedora and in other distros. For Fedora 17, it should therefor be made the default.

+

+

== Benefit to Fedora ==

+

<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->

+

Fedora users will have access to all the new language and feature enhancements provided by Java 7.

+

+

== Scope ==

+

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->

+

OpenJDK7 builds already exist in rawhide, the only work that remains is to check packages that fail to build with OpenJDK7 due to API/similar changes are fix them. This is being tracked [[Java7_Package_Rebuild_Status|here]].

+

+

== How To Test ==

+

<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.

+

+

Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.

+

+

A good "how to test" should answer these four questions:

+

+

0. What special hardware / data / etc. is needed (if any)?

+

1. How do I prepare my system to test this feature? What packages

+

need to be installed, config files edited, etc.?

+

2. What specific actions do I perform to check that the feature is

+

working like it's supposed to?

+

3. What are the expected results of those actions?

+

+

-->

+

+

* Install {{package|java-1.7.0-openjdk}}

+

* Run (as root) 'alternatives --config java' and select the 1.7 version

+

* Run 'java -version' to ensure that it is correct

+

+

+

== User Experience ==

+

<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->

+

By default, users will have access to all of the new features that version 7 of the language provides.

+

+

== Dependencies ==

+

<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->

+

+

No new dependencies are needed for java-1.7.0-openjdk.

+

+

== Contingency Plan ==

+

<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->

+

+

Everything built with Java 6 is usable with Java 7, so no contingency should be needed. For sanity, all Java packages should be built with OpenJDK7 (locally or in Koji) to ensure that there are no API discrepencies. Such discrepencies will be few and far given how compatible 7 is with 6.

+

+

== Documentation ==

+

<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->

+

+

New features in OpenJDK7 are listed on [http://openjdk.java.net/projects/jdk7/features/].

+

+

== Release Notes ==

+

<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->

+

<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->

+

+

+

== Comments and Discussion ==

+

* See [[Talk:Features/Java7]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

+

+

+

[[Category:FeatureAcceptedF17]]

+

<!-- When your feature page is completed and ready for review -->

+

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

+

<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->

+

<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

+

+

+

<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->

Owner

Current status

Detailed Description

OpenJDK7 has been available as a tech preview in Fedora 16 since GA.

In Fedora 16, the default JDK has been kept as OpenJDK6 due to the relative untested state of OpenJDK7 at the time. OpenJDK7 has received a fair bit of testing since in Fedora and in other distros. For Fedora 17, it should therefor be made the default.

Benefit to Fedora

Fedora users will have access to all the new language and feature enhancements provided by Java 7.

Scope

OpenJDK7 builds already exist in rawhide, the only work that remains is to check packages that fail to build with OpenJDK7 due to API/similar changes are fix them. This is being tracked here.

How To Test

User Experience

By default, users will have access to all of the new features that version 7 of the language provides.

Dependencies

No new dependencies are needed for java-1.7.0-openjdk.

Contingency Plan

Everything built with Java 6 is usable with Java 7, so no contingency should be needed. For sanity, all Java packages should be built with OpenJDK7 (locally or in Koji) to ensure that there are no API discrepencies. Such discrepencies will be few and far given how compatible 7 is with 6.