Same reason as in gh-28308 introduced with d6a869fa98eaeb3c180a8a3d94dcce8e3f51e204
@wilkinsona exclusion was removed in 2fb8c8d27e277150c4f5bf1037f5c76e24292a42
Comment From: martin-v
I checked the complete 2fb8c8d27e277150c4f5bf1037f5c76e24292a42 but this was the only one I found.
Comment From: wilkinsona
Thanks very much. I missed that when tidying up the exclusions.
Comment From: philwebb
It looks like this one might be required after all, possibly the exclusion as well. The dependency is required for xmlunit which has the following in its POM:
<profiles>
<profile>
<id>java9+</id>
<activation>
<jdk>[9,)</jdk>
</activation>
<dependencies>
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>
<optional>true</optional>
</dependency>
</dependencies>
</profile>
</profiles>
I suspect that Maven users who are running Java 9+ will end up getting the wrong dependency.
Comment From: philwebb
I think we should leave this one in and fix #28332 to allow it.