Hi Gary,
Thanks for your review, for Xalan-J XSLT 3.0 alpha RC2.
As one of the inputs for release notes, for Xalan-J XSLT 3.0 alpha
release, I've given release version name as xslt3.0_alpha1 within all
the jira issues that we've created for Xalan's XSLT 3.0 development.
There are lot of mails that've been sent by Apache jira system due to
this activity. My apologies for the volume of these mails, if that's
annoying.
There're 2,3 open jira issues that were assigned to you for these
activities, have now been assigned to me, due to the jira bulk update
that I did from Apache Xalan-J jira project. These and any other
Xalan-J jira issues may be assigned to you or to any other Xalan-J
team member.
I'll work on solving the issues, as mentioned within your review
comments within mail trail. I'll share the details for you to review
again, when I've completed these activities.
On Sat, Feb 28, 2026 at 7:03 PM Gary Gregory <[email protected]> wrote:
> Thank you for preparing the release candidate.
>
> The VOTE email should contain the SVN revision of the folder so we can
> be precise on what we're voting on, especially when we progress from
> one release candidate to the next.
>
> For example, here's an example of a VOTE email from Apache Commons:
> https://lists.apache.org/thread/dn7k4xxz02v60g1bh6zjo4k9sljtk9qn
>
> I am testing the source zip file.
>
> I usually verify a SHA512 file using `shasum --check` on macOS, but in
> this case, I couldn't:
>
> shasum --check xalan-j_xslt3.0_src_alpha_rc2.zip.sha512
> shasum: xalan-j_xslt3.0_src_alpha_rc2.zip.sha512: no properly
> formatted SHA checksum lines found
>
> Eyeballing the SHA512 file by comparing it with _seems_ ok:
>
> shasum -a 512 xalan-j_xslt3.0_src_alpha_rc2.zip
> 52e51d3cf20ad4c84391ac66e85e069023f2cb72fbda46b73041060f3dbb19c3110344c1888a8101ce117003f1da2325585d1d69498acc698e96719c236d58ac
> xalan-j_xslt3.0_src_alpha_rc2.zip
>
> - ASC file OK
> - NOTICE file OK
> - TODO: The source zip is missing a RELEASE-NOTES.txt file of some kind.
> - Why is this file included: LICENSE.xpath31_types-1.0.html ? A
> release notes file would help explain. Having the file in HTML is
> unhelpful IMO, especially since our license is in plain text.
> - Maybe rename README to BUILDING.txt, consider using Markdown (BUILDING.md).
>
> The instructions in README don't work:
>
> mvn clean install test -Dtest=AllXalanXSLT3Tests
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 0.711 s
> [INFO] Finished at: 2026-02-28T08:29:09-05:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project xalan-java: Could not
> resolve dependencies for project
> org.apache.xsl:xalan-java:jar:3.0.1-SNAPSHOT
> [ERROR] dependency: org.apache.xerces:xalan-java_xpath31_types:jar:0.1
> (compile)
> [ERROR] Could not find artifact
> org.apache.xerces:xalan-java_xpath31_types:jar:0.1 in
> xalan_maven_repos (file:///Users/garygregory/rc/x/libs)
> [ERROR] Could not find artifact
> org.apache.xerces:xalan-java_xpath31_types:jar:0.1 in central
> (https://repo.maven.apache.org/maven2)
>
> IMO we should provide build instructions such that users can build
> from scratch, whether they are applications or downstream
> distributions (like some Linux distributions like to build everything
> from source).
>
> HTH,
> Gary
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
