- From: Imsieke, Gerrit, le-tex <gerrit.imsieke@le-tex.de>
- Date: Sun, 7 Dec 2025 15:59:18 +0100
- To: xproc-dev@w3.org
A customer of ours, having switched to Java 25 on the Mac, recently reported that the XML parser (supposedly xerces) didn’t observe the increased entity expansion limit any more that our Calabash invocation script set via -Djdk.xml.entityExpansionLimit=$ENTITYEXPANSIONLIMIT=2147483647 I don’t remember how he solved it. Maybe by switching back to an older Java version. Therefore I wouldn’t recommend to *require* Java 25 for XML Calabash 3 to run. But making Java 17 a requirement is absolutely Ok for us. Gerrit On 06.12.2025 13:42, David Birnbaum wrote: > No objection here. FWIW (although nobody asked), also no objection with targeting the most recent LTS, which is 25. > >> On Dec 6, 2025, at 7:31 AM, Norm Tovey-Walsh <ndw@nwalsh.com> wrote: >> >> Hello, >> >> Apologies for this slightly off-topic question. >> >> I’m very tempted to update XML Calabash 3.x so that Java 17 is required. This would simplify some things in the build and make the deprecation warnings associated with Java 8 go away. >> >> I observe that there are already extension steps that require Java 17 (the Polyglot and RDF steps), and Saxon 13, when it is eventually released, will require Java 17. So at that point, my hand will be forced. >> >> Is anyone going to be inordinately inconvenienced by a move to Java 17? >> >> Be seeing you, >> norm >> >> -- >> Norm Tovey-Walsh <ndw@nwalsh.com> >> https://norm.tovey-walsh.com/ >> >>> A facility for quotation covers the absence of original thought.--Lord >>> Peter Wimsey >>
Received on Sunday, 7 December 2025 14:59:25 UTC