#178 Utilize Jython 2.7 when it becomes available
Closed: Invalid Opened by mharmsen.

PROBLEM:

The PKI deployment utility currently utilizes Python 2.7 coding standards for installation, and invokes Jython 2.2 (the latest available version as of Fedora 17) as a separate process for configuration.

The problem is that Jython 2.2 is VERY old and lacks a number of handy features (e. g. - logging) found in Jython 2.5.

However, it was recently announced that Jython 2.7 has been funded:

  • http://en.wikipedia.org/wiki/Jython

If Jython 2.7 works as advertised AND can rapidly be adopted by Fedora in time for RHEL 7, it should be considered to make the PKI deployment program dependent exclusively on Jython 2.7 such that a single process could be used end-to-end to both install and configure CA, KRA, OCSP, and TKS subsystems.


Jython 2.7a2 Has Been Released (May 30, 2012)

See http://www.jython.org/

we will be moving away from jython.

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: UNTRIAGED

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/750

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