lyca commented on PR #116: URL: https://github.com/apache/xerces-j/pull/116#issuecomment-5507634044
Isolating the test with fork="yes" and proper setUp/tearDown definitely fixes the JVM state leakage :+1: As a possible alternative, this could be solved at the root by exposing use-code-point-count-for-string-length as a proper Xerces validation feature rather than a global System Property. This entirely removes the need to fork the JVM and allows the behavior to be toggled cleanly for a single validator instance via setFeature(). I've isolated this approach (which remains 100% backward compatible) into a single commit here: https://github.com/lyca/xerces-j/tree/fix-surrogate-pair-test -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
