XercesUsageTestCase is the source of a lot of problems due to its use of Shrinkwrap resolvers. That use doesn't seem reliable in general on ci.wildfly.org, and it adds complication to how we manage our poms because it loads the tesuite/integration/basic/pom.xml with the expectation that pom is designed with such use in mind. (It's not.)

We've also gotten complaints about the loaded artifact having CVEs.

Since WFLY-18644 I don't see the point of this test. We don't provide xerces ourselves, so it's no longer testing packaged xerces vs our own. We use the JDK jaxp. Perhaps packaged xerces could have an issue with that, but there are probably thousands of artifacts that if packaged might conflict with what comes from Java SE, and we don't have tests to check that they don't.

It's been a year since we've removed xerces from our dist and we've not encountered real issues, so at this point I think we've tested enough.