Hi Gary,
Following are few other information about Xalan-J XSLT 3.0 alpha1 release,
Jira issues addressed, document :
https://xalan.apache.org/xalan-j/xsl3/release/alpha1/xalanj_xslt3.0_alpha1_jira_issue_list.pdf
Release notes document
:https://xalan.apache.org/xalan-j/xsl3/release/alpha1/RELEASE-NOTES.txt
On Tue, Mar 3, 2026 at 8:32 PM Mukul Gandhi <[email protected]> wrote:
> I've prepared Xalan-J XSLT 3.0 alpha1 RC3, for review, with
> following various details about this RC.
>
> Web location,
> https://dist.apache.org/repos/dist/dev/xalan/j/xslt3.0/alpha1/rc3/
> [svn revision 82834]
>
> After producing various Xalan-J XSLT 3.0 release artifacts wrt this
> alpha1 RC, I've verified on my local the integrity of many of these
> release artifacts, as follows,
>
> I did verify as per following details on Windows and WSL, and I think
> these should work fine on macOS as well.
>
> (1) Verification of, developer build from, Xalan-J XSLT 3.0
> development src code (dev repos branch, xalan-j_xslt3.0_mvn)
>
> d:\path\xalan-j_xslt3.0_mvn>set JAVA_HOME=d:\jdk-1.8
>
> d:\path\xalan-j_xslt3.0_mvn>mvn clean install test -Dtest=AllXalanXSLT3Tests
>
> [INFO] Tests run: 1405, Failures: 0, Errors: 0, Skipped: 0, Time
> elapsed: 31.17 s - in org.apache.xalan.tests.main.AllXalanXSLT3Tests
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1405, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 48.211 s
> [INFO] Finished at: 2026-03-03T19:40:28+05:30
> [INFO]
> ------------------------------------------------------------------------
>
>
> (2) Signature verification
>
> Verified on both, Windows and Linux [WSL] platforms, with following commands
>
> 1) gpg --verify xalan-j_xslt3.0_src_alpha1_rc3.zip.asc
>
> gpg: assuming signed data in 'xalan-j_xslt3.0_src_alpha1_rc3.zip'
> gpg: Signature made 03/03/26 19:21:00 India Standard Time
> gpg: using RSA key 4D8FB572FB6ADCFD69CBFE0D7B2586A6B5E25C3D
> gpg: Good signature from "Mukul Gandhi (CODE SIGNING KEY) <[email protected]>"
>
>
> 2) gpg --verify xalan-j_xslt3.0_src_alpha1_rc3.tar.gz.asc
>
> gpg: assuming signed data in 'xalan-j_xslt3.0_src_alpha1_rc3.tar.gz'
> gpg: Signature made 03/03/26 19:20:53 India Standard Time
> gpg: using RSA key 4D8FB572FB6ADCFD69CBFE0D7B2586A6B5E25C3D
> gpg: Good signature from "Mukul Gandhi (CODE SIGNING KEY) <[email protected]>"
>
> 3) gpg --verify xalan-java-3.0.1-SNAPSHOT.jar.asc
>
> gpg: assuming signed data in 'xalan-java-3.0.1-SNAPSHOT.jar'
> gpg: Signature made 03/03/26 19:30:49 India Standard Time
> gpg: using RSA key 4D8FB572FB6ADCFD69CBFE0D7B2586A6B5E25C3D
> gpg: Good signature from "Mukul Gandhi (CODE SIGNING KEY) <[email protected]>"
>
>
> (3) SHA512 checksum, verification
>
> Contents, of xalan-j_xslt3.0_src_alpha1_rc3.zip.sha512, distributed
> with Xalan-J release
>
> xalan-j_xslt3.0_src_alpha1_rc3.zip: F160EEB6 17D29DCD 144E27DC D2F9B725
> 2FE7B8FF 075AB21A D3C55286 08DA7285
> E3EC92C2 0C6B71E2 3C9F56CC D5297580
> 95CE5270 30D2004B 865F1264 6C1A9A9D
>
> (I) Windows
>
> d:\path>CertUtil -hashfile xalan-j_xslt3.0_src_alpha1_rc3.zip SHA512
>
> SHA512 hash of xalan-j_xslt3.0_src_alpha1_rc3.zip:
> f160eeb617d29dcd144e27dcd2f9b7252fe7b8ff075ab21ad3c5528608da7285e3ec92c20c6b71e23c9f56ccd529758095ce527030d2004b865f12646c1a9a9d
> CertUtil: -hashfile command completed successfully
>
> (II) Linux [WSL]
>
> $ openssl sha512 xalan-j_xslt3.0_src_alpha1_rc3.zip
>
> SHA512(xalan-j_xslt3.0_src_alpha1_rc3.zip)=
> f160eeb617d29dcd144e27dcd2f9b7252fe7b8ff075ab21ad3c5528608da7285e3ec92c20c6b71e23c9f56ccd529758095ce527030d2004b865f12646c1a9a9d
>
>
> Please review this RC from your side, and let us know your review
> comments for possible improvements.
>
> Here's my +1, to make Xalan-J XSLT 3.0 alpha1 release, as per this RC.
>
> Great work everyone.
>
> Many thanks.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
