Bug 838084 - icedtea-web: use java-1.7.0-openjdk instead of java-1.6.0-openjdk
icedtea-web: use java-1.7.0-openjdk instead of java-1.6.0-openjdk
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: icedtea-web (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Deepak Bhole
Lukas Zachar
: 865788 (view as bug list)
Depends On:
Blocks: 790092 886216
  Show dependency treegraph
Reported: 2012-07-06 09:08 EDT by Tomas Hoger
Modified: 2013-02-21 06:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 06:04:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Hoger 2012-07-06 09:08:58 EDT
Description of problem:
Red Hat Enterprise Linux 6.3 RHEA-2012:0981 introduced java-1.7.0-openjdk packages to Red Hat Enterprise Linux 6:


icedtea-web browser plugin use hard-coded path to JRE that is set at built time.  Current Red Hat Enterprise Linux 6 version uses java-1.6.0-openjdk.  This should be changed to use java-1.7.0-openjdk instead.
Comment 2 RHEL Product and Program Management 2012-09-07 01:37:00 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 4 Tomas Hoger 2012-10-12 09:48:52 EDT
*** Bug 865788 has been marked as a duplicate of this bug. ***
Comment 20 errata-xmlrpc 2013-02-21 06:04:11 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.