Split pki-base into Java and Python client packages

[pki-bot]

This issue was migrated from Pagure Issue #1399. Originally filed by edewata (@edewata) on 2015-06-02 20:32:21:

• Closed as Fixed
• Assigned to vakwetu (@vakwetu)

---

The current pki-base contains both the client libraries for Java and Python. The Java library seems to have dependencies on a large number of packages, which may be too big for another application wanting to just use the Python library.

To solve the problem, the pki-base should be split into pki-java-client and pki-python-client packages. This way other Python applications can depend on pki-python-client without requiring Java. For backward compatibility the new pki-base should depend on both client packages.

Proposed milestone: 10.3

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-06-08 20:44:11

Per CS/DS meeting of 06/08/2015: 10.3

[pki-bot]

Comment from vakwetu (@vakwetu) at 2015-08-18 17:13:16

Also, it seems that pki-base has a bunch of dependencies that really should just be in pki-server, like all the resteasy stuff. This should be leaned up too.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-01-27 01:13:35

Internal change

[pki-bot]

Comment from vakwetu (@vakwetu) at 2016-03-01 19:38:29

Checked into master:

• 49e4fff

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-03-07 21:56:58

Additionally, the 'pki-base' build and runtime requirements needed to be updated to 'pki-base-java' in 'master':

commit 84eaa4e
Author: Matthew Harmsen mharmsen@pki.usersys.redhat.com
Date: Mon Mar 7 10:57:07 2016 -0700

Change 'pki-base' --> 'pki-base-java' for build and runtime dependencies

PKI TRAC Ticket 1399 - Split pki-base into Java and Python client packages

[pki-bot]

Comment from edewata (@edewata) at 2017-02-27 14:08:42

Metadata Update from @edewata:

• Issue assigned to vakwetu
• Issue set to the milestone: 10.3.0.a1