Hello Amanda,

Even less of an expert than David (honest!), but I've been moved along to
Java 17 as the 'assumed minimum', and I'm slow (at least in that area).

I could probably also be convinced to move that line up -- while I will
still probably be slow.

Cheers, Wendell

On Sat, Sep 27, 2025 at 7:30b/PM David Birnbaum djbpitt@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Using Java 25 here. No objection, of course, to supporting older versions,
> as well, but I have no need for it.
>
> Just one data point b&
>
> On Sat, Sep 27, 2025 at 7:26b/PM Amanda Galtman galtmana@xxxxxxxxx <
> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Hi, all.
>>
>> Are you an XSpec user who wants to generate XSLT code coverage reports?
>> If so, is it important for you to be able to use Java 11 when generating
>> such reports?
>>
>> Background: We just released XSpec v3.3 yesterday, and we want the next
>> version to drop support for Java 8. The question is whether the minimum
>> Java version should become 11 or 17. In most areas, the Java requirements
>> of XSpec are really the Java requirements of underlying XSLT/XQuery/XProc
>> processors. Code coverage reporting is different, because XSpec has its
own
>> Java code.
>>
>> By way of comparison: XML Calabash 3 requires Java 11; BaseX 12.0
>> requires Java 17; Oxygen 27.1 bundles Java 17; Saxon 12.9 says it is
usable
>> with Java 8 but is built/tested with Java 21.
>>
>> Thanks for any input.
>>
>> Amanda
>>
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/174322> (by
> email <>)
>


--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...