Update jakarta.xml.bind-api to 3.0+

[pigelvy]

Hi,

XMLUnit is currently using the jakarta.xml.bind:jakarta.xml.bind-api r2.3.3, which uses the legacy package javax.xml.bind.

Since Jakarta XML Binding 3.0, the package was changed to jakarta.xml.bind.

I think it's time to get away from the old javax.* world and embrace the new jakarta.* one. Several other projects have already migrated and because Maven groupId/artifactId have not changed, we can't use both at the same time.

IMO, it would be a step forward to update this API.

It would also be a step forward to update Java to 11+. It's about time to move on and let Java 8 go.

Regards

[bodewig]

org.xmlunit:xmlunit-jakarta-jaxb-impl depends on 3.0.1 and is what you need to add as a dependency. See https://github.com/xmlunit/user-guide/wiki/JAXB#i-want-to-use-jakartaxmlbind

[pigelvy]

Thanks for the info.

One remark though... Is it normal for org.xmlunit:xmlunit-jakarta-jaxb-impl to depend on the JAXB implementation
org.glassfish.jaxb:jaxb-runtime in scope compile?

It forces the users to use it, or to explicitly exclude it.

[bodewig]

Hmm, at least for XMLUnit itself it would be enough to use the compile test scope.

The alternative is that everybody is forced to explicitly specify an implementation, isn't it? If we changed it, the next release would break things for the existing users of xmlunit-jakarta-jaxb-impl who rely on the transitive dependency.

[pigelvy]

Indeed, changing the scope of the dependency would introduce a breaking change. However, it is a small breaking change that is easy to justify, document and fix.

Furthermore, working with an API and being agnostic of the runtime implementation is the whole point of an API.
All the Jakarta specifications seem to work that way. People must already know about that...

[bodewig]

Basically I've been verifying my understanding, thanks.

Note that I personally don't use JAXB (neither version) so really only perform the basic testing provided by the unit tests.