You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apache commons-lang 2.x releases are no longer compatible with Java 11 (due to usage of assert and enum as identifiers), and fedora packages are all getting ported to commons-lang3.
I did a quick search of the PKI sources and found no usage of APIs that were removed with commons-lang3, so porting PKI to the new version should be straightforward:
change dependency in pom.xml files to org.apache.commons:commons-lang3
change import statements in Java files: "s/org\.apache\.commons\.lang\./org.apache.commons.lang3./"
I'm not sure if other parts of the build machinery need to be adapted as well (I'm not that familiar with CMake).
There's also a Java SIG tracking issue for porting packages to commons-lang3.
The text was updated successfully, but these errors were encountered:
This issue was migrated from Pagure Issue #3205. Originally filed by decathorpe (@decathorpe) on 2020-08-13 11:50:55:
apache commons-lang 2.x releases are no longer compatible with Java 11 (due to usage of
assert
andenum
as identifiers), and fedora packages are all getting ported to commons-lang3.I did a quick search of the PKI sources and found no usage of APIs that were removed with commons-lang3, so porting PKI to the new version should be straightforward:
pom.xml
files toorg.apache.commons:commons-lang3
"s/org\.apache\.commons\.lang\./org.apache.commons.lang3./"
I'm not sure if other parts of the build machinery need to be adapted as well (I'm not that familiar with CMake).
There's also a Java SIG tracking issue for porting packages to commons-lang3.
The text was updated successfully, but these errors were encountered: