jakarta.activation-api classpath collision with jakarta.activation

The jackson-module-jaxb-annotations artifact pulls in the jakarta.activation:jakarta.activation-api dependency.

This causes classpath collisions for the activation api classes that are also included in com.sun.activation:jakarta.activation if this artifact is also a (transitive or not) dependency.

Ie. in Jetty you will get this warning at startup: [WARNING] javax.activation.ActivationDataFlavor scanned from multiple locations: jar:file:///<snip>.m2/repository/com/sun/activation/jakarta.activation/1.2.1/jakarta.activation-1.2.1.jar!/javax/activation/ActivationDataFlavor.class, jar:file:///<snip>.m2/repository/jakarta/activation/jakarta.activation-api/1.2.1/jakarta.activation-api-1.2.1.jar!/javax/activation/ActivationDataFlavor.class

The fix in similar cases seems to be to change the jakarta.activation-api dependency to jakarta.activation https://github.com/eclipse-ee4j/jaf/issues/18 https://issues.apache.org/jira/browse/SPARK-27611

Is this in scope for jackson-module-jaxb-annotations or are users of the artifact meant to manually exclude/provide the activation api classes?

[GedMarc]

Simple update to 1.2.2 on activation-api, removal of activation 😃

Please let me do this PR though, jaxb also has a funky thing on this (jaxrs base&impl)

[aelgn]

@GedMarc Aha! Thank you for bearing with me. This did indeed solve the problem 👍 🥇

For posterity:

<dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>com.fasterxml.jackson</groupId>
        <artifactId>jackson-bom</artifactId>
        <version>2.12.0-rc2</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>jakarta.activation</groupId>
        <artifactId>jakarta.activation-api</artifactId>
        <version>2.0.0</version>
      </dependency>
      <dependency>
        <groupId>jakarta.xml.bind</groupId>
        <artifactId>jakarta.xml.bind-api</artifactId>
        <version>3.0.0</version>
      </dependency>
    </dependencies>
  </dependencyManagement>