Jaxb-runtime transitive dependencies are ignored when building a Maven project on JDK11 with a dependency to Hibernate ORM
Description
Somehow, the POM for jaxb-runtime is considered invalid, but only if you run Maven with JDK11. As a result, attempting to build a project that depends on Hibernate ORM will produce the following warning:
1
[WARNING] The POM for org.glassfish.jaxb:jaxb-runtime:jar:2.2.11 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details... which is obviously a big deal, because ORM does rely on these transitive dependencies (among which jaxb-core).
In practice, the application may work fine, dependening on how it is booted. In Hibernate Search, all of our tests pass, except the ones using Envers. But then we don't really start Hibernate ORM like a real application would (we skip some steps) so maybe application are more affected by this bug than Hibernate Search.
Regarding why the POM for jaxb-runtime is considered invalid, this demonstrates the problem (you need to use JAVA10 or above for the problem to appear):
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
cd $(mktemp -d) ; mvn -q dependency:copy '-Dartifact=org.glassfish.jaxb:jaxb-runtime:2.2.11:pom' -DoutputDirectory=. ; mvn dependency:tree -f 'jaxb-runtime-2.2.11.pom'
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. @
[ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/yrodiere/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.11/jaxb-parent-2.2.11.pom, line 188, column 29
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.glassfish.jaxb:jaxb-runtime:2.2.11 (/tmp/tmp.h8YtWpnCh3/jaxb-runtime-2.2.11.pom) has 1 error
[ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/yrodiere/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.11/jaxb-parent-2.2.11.pom, line 188, column 29
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExceptionUpgrading to the very next version, 2.3.0-b170127.1453, seems to fix the problem. But we've had trouble in the past with using newer versions of JAXB in ORM, in particular in an OSGi environment...
Environment
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00)
Same goes with the latest, Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)
openjdk version "11" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
Status
Assignee
Reporter
Fix versions
Labels
backPortable
Suitable for new contributors
Requires Release Note
backportDecision
Components
Priority
Major