JAXB v3

[KevinvdBosch]

This pull request contains changes from using jaxb v2 to v3. This means converting the use of javax packages to jakarta.

The only problem with this is that xsd files can't be found anymore when they are in separate modules. It seems that maven can't merge them properly anymore.

A temporary fix could be to duplicate the xsd files where needed. This will make all unit tests pass.

The only thing that still remains broken is the creation of the zip file containing all schema files in the deegree-core-schema module.

depends on #1452

[stephanr]

The only problem with this is that xsd files can't be found anymore when they are in separate modules. It seems that maven can't merge them properly anymore.

Could this be related to our custom resolver configured here:

deegree3/pom.xml

Line 97 in 86bbe91

<catalogResolver>org.deegree.uncoupled.jaxb.CatalogResolver</catalogResolver>

Have you checked whether this interface also needs to be changed?

deegree3/uncoupled/deegree-jaxb-resolver/src/main/java/org/deegree/uncoupled/jaxb/CatalogResolver.java

Line 69 in 86bbe91

public class CatalogResolver extends com.sun.org.apache.xml.internal.resolver.tools.CatalogResolver {

[tfr42]

Hi @KevinvdBosch, thank you for providing that PR.
To make it easier to merge the proposed changes would it be possible that you

• split the PR related to JAXB 2 to 3 migration from
• changing old JAVA EE API like javax.mail and javax.activation (imports and dependencies)?
• And also create a seperate PR for changing com.sun.xml.bind:jaxb-impl to org.glassfish.jaxb:jaxb-runtime (please see Fix for dependency conflicts introduced with ehcache 3.x upgrade (PR #1441) #1459 for more information)