#352 Dogtag 10: Consider repackaging ".so" libraries as a resource within a JNI jar file . . .
Closed: migrated by dmoluguw. Opened by mharmsen.

Per discussions pertaining to "https://fedoraproject.org/wiki/User:Akurtakov/JavaPackagingDraftUpdate#Example", consider changing the 'pki-symkey' and 'jss' JNI packages to contain their own ".so".

Since JNI rpms are platform dependent, this would imply the following changes:

||Component||Platform||Current Layout||Proposed Layout||
||JSS||32-bit i686||/usr/lib/java/jss4.jar /usr/lib/jss/libjss4.so||/usr/lib/java/jss4.jar||
||JSS||64-bit x86_64||/usr/lib64/java/jss4.jar /usr/lib64/jss/libjss4.so||/usr/lib/java/jss4.jar||
||pki-symkey||32-bit i686||/usr/lib/java/symkey.jar /usr/lib/jss/libsymkey.so||/usr/lib/java/symkey.jar||
||pki-symkey||64-bit x86_64||/usr/lib64/java/symkey.jar /usr/lib64/jss/libsymkey.so||/usr/lib/java/symkey.jar||

Obviously, the Java code would need to changed to work with an embedded ".so".

Packages currently utilizing this format include the 'eclipse-swt' JNI package currently bundled within the 'eclipse' SRPM.


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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata