On Tue, 22 Sep 2026, Thomas Uhle wrote:
On Mon, 3 Mar 2025, Emmanuel Bourg wrote:
On 02/03/2025 21:45, Thomas Uhle wrote:
XMLUnit version 2.9.0 (see #1099351 [1]) depends on JAXB Runtime version
2.3.3 at least. In turn, it depends on Jakarta's JAXB API which is already
packaged in Debian experimental. So could you please consider to package
version 3.0.1 matching the version of JAXB API in experimental and upload
it to experimental too.
The libjaxb-java package must stick to the javax API to preserve the
backward compatibility as we transition to the new jakarta API. Another
package should be uploaded for the jakarta version.
Should this ticket better be retitled, reassigned and transformed into an RFP
to build libjakarta-xml-bind-java then?
Okay, on Maven Central, I have seen that the artifacts provided by
libjaxb-java are provided separately for version 3.0.0 and any newer
version by org.glassfish.jaxb:jaxb-core, org.glassfish.jaxb:jaxb-runtime,
org.glassfish.jaxb:jaxb-cjx and org.glassfish.jaxb:jaxb-xjc
respectively, but everything is still built from a single source which is
to be found on Github [1].
Could introducing the new package src:jaxb-ri from which the separate
binary packages libjaxb-core-java, libjaxb-runtime-java,
libjaxb-cjx-java and libjaxb-xjc-java are built be a solution then?
Best regards,
Thomas Uhle
[1] https://eclipse-ee4j.github.io/jaxb-ri
