Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Support for OpenJDK 8 added to JPackage Utilities
OpenJDK 8 was added to RHEL 6.6 but system Java applications were not able to be run with it due to lack of OpenJDK 8 support in the _jpackage-utils_ package. This has been resolved, and the RHEL 6.7 _jpackage-utils_ package includes support for system applications to be run with OpenJDK 8.
+++ This bug was initially created as a clone of Bug #982683 +++
OpenJDK 8 changes the output format for java -fullversion, so the attached patch is needed.
Furthermore, the spec file needs to create both 1.8.0 directories:
@@ -115,10 +117,10 @@ install -dm 755 ${RPM_BUILD_ROOT}${_jvmcommonsysconfdir}
install -dm 755 ${RPM_BUILD_ROOT}${_javadir}
install -dm 755 ${RPM_BUILD_ROOT}${_javadir}-utils
install -dm 755 ${RPM_BUILD_ROOT}${_javadir}-ext
-install -dm 755 ${RPM_BUILD_ROOT}${_javadir}-{1.5.0,1.6.0,1.7.0}
+install -dm 755 ${RPM_BUILD_ROOT}${_javadir}-{1.5.0,1.6.0,1.7.0,1.8.0}
install -dm 755 ${RPM_BUILD_ROOT}${_jnidir}
install -dm 755 ${RPM_BUILD_ROOT}${_jnidir}-ext
-install -dm 755 ${RPM_BUILD_ROOT}${_jnidir}-{1.5.0,1.6.0,1.7.0}
+install -dm 755 ${RPM_BUILD_ROOT}${_jnidir}-{1.5.0,1.6.0,1.7.0,1.8.0}
install -dm 755 ${RPM_BUILD_ROOT}${_javadocdir}
install -dm 755 ${RPM_BUILD_ROOT}${_mavenpomdir}
install -dm 755 ${RPM_BUILD_ROOT}${_mavendepmapdir}
--- Additional comment from Fedora Admin XMLRPC Client on 2013-07-10 10:11:27 EDT ---
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
--- Additional comment from Mikolaj Izdebski on 2013-07-11 04:13:42 EDT ---
--- Additional comment from Mikolaj Izdebski on 2013-07-11 08:55:34 EDT ---
Fixed in jpackage-utils-1.7.5-27
--- Additional comment from Fedora Update System on 2013-07-11 09:02:11 EDT ---
jpackage-utils-1.7.5-27.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/jpackage-utils-1.7.5-27.fc19
--- Additional comment from Fedora Update System on 2013-07-22 21:12:21 EDT ---
jpackage-utils-1.7.5-27.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
--- Additional comment from Mikolaj Izdebski on 2013-07-22 23:27:26 EDT ---
I believe that this bug is fixed in jpackage-utils-1.7.5-27,
which is available in updates for Fedora 19, so I am closing this bug now.
The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=432788
Cloned to to failures in brew to use build-classpath using rhel-6 candidate.
/usr/bin/build-classpath: error: JAVAVER_LIBDIR /usr/share/java- does not exist or is not a directory
A customer also reported this possible solution:
-----
The problem is that jpackage-utils is not yet prepared for Java 8.
You have top add to your rpm jpackage-utils:
/usr/share/java-1.8.0
/usr/lib/java-1.8.0
And the difference of Java 7 and Java 8 is:
# /etc/alternatives/jre_1.7.0/bin/java -version
java version "1.7.0_65"
[...]
# /etc/alternatives/jre_1.8.0/bin/java -version
openjdk version "1.8.0_20"
[...]
Your script /usr/share/java-utils/java-functions has problems with "openjdk version" because it expects "java version" as Java 7 does.
# mkdir /usr/share/java-1.8.0
# mkdir /usr/lib/java-1.8.0
# diff /usr/share/java-utils/java-functions.orig /usr/share/java-utils/java-functions
149,150c149,150
< -e '/java \(full \)*version "/s/'$re'/<<<\1>>>/' \
< -e '/java \(full \)*version "/s/.*<<<\([^>]\{1,\}\)>>>.*/\1/p')
---
> -e '/[java|openjdk] \(full \)*version "/s/'$re'/<<<\1>>>/' \
> -e '/[java|openjdk] \(full \)*version "/s/.*<<<\([^>]\{1,\}\)>>>.*/\1/p')
------
Reproducer:
# yum install java-1.8.0-openjdk-devel ant
$ JAVA_HOME=/usr/lib/jvm/java-1.8.0 ant -version
Expected results:
Apache Ant version 1.7.1 compiled on April 26 2010
Actual results:
Error: Could not find or load main class org.apache.tools.ant.launch.Launcher
CCS has determined that this bug should be described in the RHEL 6.7 Release Notes. Please update the Doc Text field with a summary feature description.
Comment 33Mikolaj Izdebski
2015-04-03 11:05:00 UTC
*** Bug 1208832 has been marked as a duplicate of this bug. ***
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.
https://rhn.redhat.com/errata/RHEA-2015-1248.html