#771 Use headless Java for non-GUI Dogtag packages
Closed: Fixed Opened by nkinder.

In Fedora 20, there is now a headless Java package (java-1.7.0-openjdk-headless). This doesn't include any audio/video classes. The only part of Dogtag that should require any audio/video is the PKI Console.

All of our non-Console packages should require the headless Java package to try to reduce dependencies when Console isn't installed. This would result in a smaller footprint when installing individual Dogtag subsystems, such as the way FreeIPA installs the Dogtag CA.


Decreasing the size of the FreeIPA installation would be very helpful for the containerization effort.

[06/04/2014] - Moving to Milestone 10.2 (July).

This bug appears to have been previously fixed by [Bugzilla Bug #1067528 - Headless Java transition tracking bug] and https://bugzilla.redhat.com/show_bug.cgi?id=1068483 Bugzilla Bug #1068483 - pki-core: Switch to java-headless (build)requires:

* Fri Mar 28 2014 Michael Simacek <msimacek@redhat.com> - 10.2.0-0.2
- Use Requires: java-headless rebuild (#1067528)

Currently, the only PKI packages which utilize 'java' as a runtime package requirement (as opposed to 'java-headless') are:

  • PKI Console:
dogtag-pki-theme.spec - required by the 'dogtag-pki-console-theme' jar
pki-console.spec
  • PKI Migrate:
pki-migrate.spec - legacy Red Hat package not included in Fedora
  • PKI TPS:
pki-tps.spec - legacy Apache-based TPS subsystem which will no
               longer be included in Fedora (currently being
               replaced by the java Tomcat-based TPS subsystem
               included in the 'pki-core' package)

Metadata Update from @nkinder:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.2 - 07/14 (July)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1338

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata