Details
-
Enhancement
-
Resolution: Done
-
Major
-
7.12.0.Final
-
None
-
NEW
-
NEW
Description
I was looking through my dependencies, as I was upgrading to the new JAXB version (2.3.1) and I noticed a few legacy-looking dependencies pulling in an older version (2.3.0, but thats another issue). To me it seems, that optaplanner-persistence-jaxb pulls in wrong JAXB artifacts with wrong scope.
According to the JAXB developers, the artifact names have changed .
My local testing suggests, that the JAXB dependencies of optaplanner-persistence-jaxb can be heavily streamlined, as my local testing with
$ mvn test -Denforcer.fail=false
succeeded.
I removed:
- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec
- com.sun.xml.bind:jaxb-core
- com.sun.xml.bind:jaxb-impl
- javax.activation:activation
And added:
- javax.xml.bind:jaxb-api:2.3.1
- org.glassfish.jaxb:jaxb-runtime:2.3.1 (in test scope)
I don't know, which artifacts are being pulled in by other JBoss projects, as I only use optaplanner-persistence-jaxb with dependencies in that regard.