Github user HansBrende commented on the issue:
https://github.com/apache/any23/pull/132
ALSO: it appears that `javax.activation:activation:1.1.1` has been replaced
by `com.sun.activation:javax.activation:1.2.0` and
`javax.activation:javax.activation-api:1.2.0`. However, I'm a bit fuzzy on how
this works because it appears that the `javax.activation-api` sources are a
subset of the `javax.activation` sources (i.e., `javax.activation:1.2.0` does
not *depend* on `javax.activation-api:1.2.0`, but rather simply copies the
source files... I think.)
In any case, `org.glassfish.jaxb:jaxb-runtime:2.3.1` *depends on*
`javax.activation:javax.activation-api:1.2.0`, but does *not* depend on
`com.sun.activation:javax.activation:1.2.0`. Leading me to believe that if we
include both `jaxb-runtime:2.3.1` and `javax.activation:1.2.0`, we might have
to exclude `javax.activation-api` from `jaxb-runtime` to avoid duplicate
classes?
Cf.
https://stackoverflow.com/questions/46493613/what-is-the-replacement-for-javax-activation-package-in-java-9
Cf.
https://stackoverflow.com/questions/52921879/migration-to-jdk-11-has-error-occure-java-lang-noclassdeffounderror-javax-acti
Cf.
https://stackoverflow.com/questions/48204141/replacements-for-deprecated-jpms-modules-with-java-ee-apis
Cf. https://mvnrepository.com/artifact/org.glassfish.jaxb/jaxb-runtime/2.3.1
---
