Re: [xsl] XSpec/XSLT code coverage and Java version

Subject: Re: [xsl] XSpec/XSLT code coverage and Java version
From: "Amanda Galtman galtmana@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 29 Oct 2025 11:45:08 -0000
Alan and Adam, thanks for your helpful replies adding to the earlier ones.

Conclusion: We decided to use Java 17 as the required minimum for the next
XSpec version.

Regards,
Amanda


On Monday, October 6th, 2025 at 1:03 PM, Adam Retter
adam.retter@xxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> My advice would be to use the absolute minimum that you can get away
> with. If your dependencies require Java 17 as a minimum, then I would
> recommend to use that.
>
> On Mon, 6 Oct 2025 at 13:42, Amanda Galtman galtmana@xxxxxxxxx
> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx wrote:
>
> > David and Wendell,
> >
> > Thanks for providing data points! If you two are a representative sample,
then switching to Java 17 as the assumed minimum should be fine.
> >
> > Regards,
> > Amanda
> >
> > On Monday, September 29th, 2025 at 12:08 PM, Wendell Piez
wapiez@xxxxxxxxxxxxxxx xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx wrote:
> >
> > 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
> > > EasyUnsubscribe (by email)
> >
> > --
> > ...Wendell Piez... ...wendell -at- nist -dot- gov...
> > ...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
> > ...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...
> > XSL-List info and archive
> > EasyUnsubscribe (by email)
> >
> > XSL-List info and archive
> > EasyUnsubscribe (by email)
>
>
>
>
> --
> Adam Retter
>
> skype: adam.retter
> tweet: adamretter
> http://www.adamretter.org.uk

Current Thread