I am using JHOVE as part of our infrastructure to validate digitized images before publishing them in our institutional repository. During the upgrade of this infrastructure I ran into issues regarding
the transition of Java EE to Jakarta EE which brings us new Java package names and new Maven coordinates for a lot of broadly used Java libraries.
JHOVE has a dependency to the older version the JAXB framework (using the javax.xml.bind package name). Since only one small function of this framework is used (DatatypeConverter.printHexBinary(byte[]), I suggest to reimplement this function and remove the dependency to JAXB completely.
carlwilson
commented
4 months ago
I am using JHOVE as part of our infrastructure to validate digitized images before publishing them in our institutional repository. During the upgrade of this infrastructure I ran into issues regarding the transition of Java EE to Jakarta EE which brings us new Java package names and new Maven coordinates for a lot of broadly used Java libraries.
JHOVE has a dependency to the older version the JAXB framework (using the
javax.xml.bindpackage name). Since only one small function of this framework is used(DatatypeConverter.printHexBinary(byte[]), I suggest to reimplement this function and remove the dependency to JAXB completely.