Jackson 1 is no longer maintained (the last release was v1.9.13 in 2013). Update Dogtag to use Jackson 2.
PR: https://github.com/dogtagpki/pki/pull/68
Metadata Update from @ftweedal: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Pushed to master:
commit 0ce48906d4bd060fe634d18f1cff5fe8d6218808 Author: Fraser Tweedale <ftweedal@redhat.com> Date: Wed Oct 17 12:21:50 2018 +1100 Fix Python KeyClient KeyRequestResponse parsing The Resteasy Jackson 2 provider handles null fields differently from the Jackson 1 provider: null fields are included in the serialised JSON with a 'null' value, instead of being omitted. Update the KeyRequestResponse processing to handle both schemas. Fixes: https://pagure.io/dogtagpki/issue/3069 commit ec6b06aff21f3a24f060af0b68f2eb7aa1f28154 Author: Endi S. Dewata <edewata@redhat.com> Date: Thu Aug 2 16:58:48 2018 +0200 Updated Jackson dependency The spec template has been modified to depend on Jackson 2. Part of: https://pagure.io/dogtagpki/issue/3069 commit baf22bd60bc45e4c12a340b8aeb641611c48ff40 Author: Fraser Tweedale <ftweedal@redhat.com> Date: Wed Jul 25 16:49:42 2018 +1000 Use Jackson 2 instead of Jackson Jackson 1 is no longer maintained (the last release was v1.9.13 in 2013). Update Dogtag to use Jackson 2. Update scripts and changes for Debian (if required) will be provided in later commits. Part of: https://pagure.io/dogtagpki/issue/3069
Metadata Update from @ftweedal: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
just for the record, I noticed this commit by accident, and checked all the jackson2 jar names and they match with the commit so no changes should be needed for Debian
resteasy needs to add the jackson2 provider, but that's irrelevant here (and I'll fix that with the next upload)
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/3338
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.