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
The following additional JAXB dependencies are required to run e.g. Input.fromJaxb(...) in Java 9+:
jaxb-core
jaxb-impl
activation
In xmlunit-core/pom.xml, these are already listed, but are only available for the xmlunit internal tests.
External Maven projects adding a dependency on xmlunit therefore miss these libraries, because test scoped dependencies are not transitive. I would appreciate, if
they could be either declared as runtime scoped dependencies (for Java 9+)
or marked as optional, including some documentation that the JAXB features require adding these additional dependencies manually
The text was updated successfully, but these errors were encountered:
You are certainly right in that JAXB becomes an optional dependency of core in Java9+. So far I assumed that anybody who wants to test the XML serialization of an object - this is what fromJaxb does would be testing code that already depended on JAXB anyway - so didn't really think about making the dependency explicit.
The following additional JAXB dependencies are required to run e.g.
Input.fromJaxb(...)
in Java 9+:jaxb-core
jaxb-impl
activation
In xmlunit-core/pom.xml, these are already listed, but are only available for the xmlunit internal tests.
External Maven projects adding a dependency on xmlunit therefore miss these libraries, because
test
scoped dependencies are not transitive. I would appreciate, ifruntime
scoped dependencies (for Java 9+)optional
, including some documentation that the JAXB features require adding these additional dependencies manuallyThe text was updated successfully, but these errors were encountered: