From Fedora Project Wiki
(Created page with '<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. --...')
 
No edit summary
Line 48: Line 48:
== Scope ==
== 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?-->
<!-- 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?-->
The goal of IcedTea-Web is to allow faster distribution of fixes to end-user. The fast-turnaround goal also means that the project is a lot simpler to build. It involves simply checking out the sources from the mercurial repository at [http://icedtea.classpath.org/hg/] and running configure and make and make install.
The goal of IcedTea-Web is to allow faster distribution of fixes to end-user. The fast-turnaround goal also means that the project is a lot simpler to build. It involves simply checking out the sources from the mercurial repository at [http://icedtea.classpath.org/hg/ http://icedtea.classpath.org/hg/] and running configure, make and make install.


== How To Test ==
== 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.  
<!-- 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. -->


Once the RPM is built, testing simply involves installing the icedtea-web RPM. Users with the older java-1.6.0-openjdk-plugin RPM installed will automatically get icedtea-web via yum update as it virtual provides java-1.6.0-openjdk-plugin.
Once the RPM is built, testing simply involves installing the icedtea-web RPM. Users with the older java-1.6.0-openjdk-plugin RPM installed will automatically get icedtea-web via yum update as it virtual provides java-1.6.0-openjdk-plugin.


Once installed, it should be verified that it is the default plugin by running (as root):
* Once installed, verify that it is the default plugin by running (as root):
alternatives --config libjavaplugin.so[.x86_64]
alternatives --config libjavaplugin.so[.x86_64]
 
* Once set, open firefox and go to about:plugins (by typing it in the address bar and hitting enter). It should display something like:
Once set, open firefox and go to about:plugins (by typing it in the address bar and hitting enter). It should display something like:
"IcedTea-Web Plugin ..." as one of the entries.
"IcedTea-Web Plugin ..."
* Functionality can be verified by going to an applet test site like [http://javatester.org/version.html this] one.
 
as one of the entries.
 
Functionality can be verified by going to an applet test site like  


== User Experience ==
== 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. -->
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
The user experience will be largely unchanged apart from the fact the the plugin and Web Start performance will be better.


== Dependencies ==
== 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)? -->
<!-- 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 RPMS depend on icedtea-web. IcedTea-Web does not require any additional RPMS outside of what java-1.6.0-openjdk required before when it built the plugin.


== Contingency Plan ==
== 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.  -->
<!-- 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.  -->
If icedtea-web cannot be added in time, we can fall back to IcedTea6 1.9.7 for the immediate future, as it includes the plugin.


== Documentation ==
== 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. -->
<!-- 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. -->
*
* The wiki page for IcedTea-Web is located [http://icedtea.classpath.org/wiki/IcedTea-Web here]


== Release Notes ==
== 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 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. -->
<!-- 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. -->
*
* There is a fedora beats note about it [https://fedoraproject.org/wiki/Docs/Beats/Desktop#Java here]


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]]  <!-- 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 -->
* See [[Talk:Features/F15IcedTeaWeb]]  <!-- 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 -->
* Package review: [https://bugzilla.redhat.com/show_bug.cgi?id=691541 BZ691541]
* Package build: [http://koji.fedoraproject.org/koji/buildinfo?buildID=237494 http://koji.fedoraproject.org/koji/buildinfo?buildID=237494]
* Package update (already in stable): [https://admin.fedoraproject.org/updates/icedtea-web-1.0.2-2.fc15 https://admin.fedoraproject.org/updates/icedtea-web-1.0.2-2.fc15]





Revision as of 22:16, 11 April 2011


IcedTea-Web 1.0.2

Summary

This feature adds IcedTea-Web 1.0.2 to Fedora. The IcedTea-Web project provides a Free Software web browser plugin running applets written in the Java programming language and an implementation of Java Web Start, originally based on the NetX project.

Owner

  • Email: dbhole@redhat.com

Current status

  • Targeted release: Fedora 15
  • Last updated: 2011-04-11
  • Percentage of completion: 100%


Detailed Description

Previously, the Java plugin and Web Start implementations shipped in Fedora were build with the java-1.6.0-openjdk RPM as the development for those items happened in the IcedTea tree. Starting with IcedTea6 1.10 (which is in Fedora 15), the plugin and Web Start components were split into a separate project named IcedTea-Web. IcedTea-Web brings numerous functional improvements to the Java plugin and Web Start implementations in Fedora.

Benefit to Fedora

IcedTea-Web provides numerous improvements over the previous plugin and Web Start implementations shipped in Fedora. These include:

  • NetX and plugin configuration can now be specified via a deployment.properties file
  • System-level as well as user-level deployment.properties files with locked configuration are supported
  • Applications and applets can now have a Look and Feel different from rest of IcedTea-Web
  • Native directories are correctly cleaned on exit
  • Cached files with special characters in file names are now handled correctly
  • Interfaces javax.jnlp.IntegrationService and javax.jnlp.DownloadService2 are now available
  • javaws now supports a new -Xclearcache option
  • Applications with non-public main classes are now supported.
  • JNLP files containing <component-desc> as well as <application-desc> will now work
  • JNLP files referenced in the applet tag are now parsed to detect applet properties
  • Applets are now double-buffered to eliminate flicker in ones that do heavy drawing

Furthermore, because the package no longer requires a JDK rpm respin, bug fixes will be available much sooner starting with F15.

Scope

The goal of IcedTea-Web is to allow faster distribution of fixes to end-user. The fast-turnaround goal also means that the project is a lot simpler to build. It involves simply checking out the sources from the mercurial repository at http://icedtea.classpath.org/hg/ and running configure, make and make install.

How To Test

Once the RPM is built, testing simply involves installing the icedtea-web RPM. Users with the older java-1.6.0-openjdk-plugin RPM installed will automatically get icedtea-web via yum update as it virtual provides java-1.6.0-openjdk-plugin.

  • Once installed, verify that it is the default plugin by running (as root):
alternatives --config libjavaplugin.so[.x86_64]
  • Once set, open firefox and go to about:plugins (by typing it in the address bar and hitting enter). It should display something like:

"IcedTea-Web Plugin ..." as one of the entries.

  • Functionality can be verified by going to an applet test site like this one.

User Experience

The user experience will be largely unchanged apart from the fact the the plugin and Web Start performance will be better.

Dependencies

No RPMS depend on icedtea-web. IcedTea-Web does not require any additional RPMS outside of what java-1.6.0-openjdk required before when it built the plugin.

Contingency Plan

If icedtea-web cannot be added in time, we can fall back to IcedTea6 1.9.7 for the immediate future, as it includes the plugin.

Documentation

  • The wiki page for IcedTea-Web is located here

Release Notes

  • There is a fedora beats note about it here

Comments and Discussion