#109 Dogtag 10: Fix CMake to better handle JNI jar files
Closed: Fixed None Opened 9 years ago by mharmsen.

This work will be based upon:

- Bugzilla Bug #785020 - RFE: Embed "%{_jnidir}" logic inside the CMake system . .

and will include:

- integration of the 'include(GNUInstallDirs)' logic

Addtionally, based upon the document entitled
'http://fedoraproject.org/wiki/Packaging:Java#Packaging_JAR_files_that_use_JNI', I will
add the following benign informational symlinks:

- %{_libdir}/jss/jss4.jar -> %{_libdir}/java/jss4.jar
- %{_libdir}/osutil/osutil.jar -> %{_libdir}/java/osutil.jar
- %{_libdir}/symkey/symkey.jar -> %{_libdir}/java/symkey.jar

Although we could move the current location of these jars and reverse the symlink, these decisions were based upon lengthy decisions arrived at in the following bugs:

- Bugzilla Bug #665576 - "build-classpath swt" fails on 64bit
- Bugzilla Bug #734590 - Refactor JNI libraries for Fedora 16+ . . .

which are not reflected in the current Fedora JNI packaging guidelines.


Fixed in the following builds:

  • jss-4.2.6-23.fc15
  • jss-4.2.6-23.fc16
  • jss-4.2.6-23.fc17
  • jss-4.2.6-23.fc18

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: Dogtag 10.0.0.a1

4 years ago

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

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.

Login to comment on this ticket.

Metadata