Hi Elliotte, On 24.04.2026 13:06, Elliotte Rusty Harold wrote: > That said, Xerces does not have sufficient developer participation > at this time to promise quick resolution. That's one reason I'm so > wary of adding new projects that have even less commitment.
Xerces XML Commons does look like a natural home for this. If participation is the blocker, I'd be happy to help on the infrastructure side: SVN-to-Git conversion, modernizing the build. That's mechanical work, but it's the kind of thing that lowers the bar for future contributions. There's some irony in proposing this under Xerces. The library exists in part because Xerces is, these days, a transitive-dependency footgun: pulling it in silently opts an application out of JEP 185's ACCESS_EXTERNAL_* restrictions, since Xerces stays faithful to the XML spec rather than the JDK's hardened interpretation of it. A library that hardens both implementations uniformly arguably belongs under the project that maintains the one most in need of the help. Piotr --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
