dogtagpki

#330 Inconsistent references to commons JAR packages.
Closed: fixed by cipherboy. Opened by edewata.

Closed: fixed
Reopen Issue

Currently some of the code use commons-.jar, but some others use apache-commons-.jar. They are functionally identical, but it would be better to use a generic commons-*.jar that doesn't contain vendor name or version name to avoid upgrade issues.

Note that in order to be consistent on debian, we should be using the generic commons-* names.

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

We now use CMake and try to automatically detect the jar path.

Metadata Update from @cipherboy:
- Custom field proposedmilestone adjusted to None (was: Future)
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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
None
None
None
None
Normal
None
None
None
defect
General
Cleanup
Community
trivial
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.