JAXP transitive dependencies in v3 ?

[Tom Zeller]

I guess my question is : how do/should we handle transitive
dependencies on Xerces/Xalan in v3 ?

If a runtime transitive dependency on Xerces/Xalan exists, then
idp.xml.securityManager needs to be
"org.apache.xerces.util.SecurityManager", otherwise an
IllegalArgumentException is thrown :
"com.sun.org.apache.xerces.internal.util.SecurityManager cannot be
cast to org.apache.xerces.util.SecurityManager".

I ask because one of my first steps for ToU/Consent was to stand up a
simple unit test using Selenium, which is straightforward, except that
Selenium depends on HtmlUnit which depends on Xerces/Xalan.

So, this is a testing issue, but it seems we would need to exclude
transitive Xerces/Xalan dependencies in our v3 POMs in general.

Thoughts ?

Thanks.