Re: [VOTE] Release Apache Commons Validator 1.11.0 based on RC1

+1 Checks out on all fronts.

Cheers,
-Rob

> On Jul 27, 2026, at 9:38=E2=80=AFPM, Gary Gregory =
<[email protected]> wrote:
>=20
> We have fixed 28 bugs and added minor enhancements since the release
> of Apache Commons Validator 1.10.1, so I would like to release Apache
> Commons Validator 1.11.0.
>=20
> Apache Commons Validator 1.11.0 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1
> (svn revision 86283)
>=20
> The Git tag commons-validator-1.11.0-RC1 commit for this RC is
> eaee281bc5fafbfed54de52f08d6b2656d9d6b5c, which you can browse here:
>    =
https://gitbox.apache.org/repos/asf?p=3Dcommons-validator.git;a=3Dcommit;h=
=3Deaee281bc5fafbfed54de52f08d6b2656d9d6b5c
> You may checkout this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-validator.git
> --branch commons-validator-1.11.0-RC1 commons-validator-1.11.0-RC1
>=20
> Maven artifacts are here:
>    =
https://repository.apache.org/content/repositories/orgapachecommons-1955/c=
ommons-validator/commons-validator/1.11.0/
>=20
> These are the artifacts and their hashes:
>=20
> #Release SHA-512s
> #Tue Jul 28 01:27:00 UTC 2026
> =
commons-validator-1.11.0-bin.tar.gz=3Dde5b755fe96916208bf38d608940d1a258c0=
1964b21e72fae4cd892c8a3f8cb9699778857d59492cccbe985fe7b068c0968ece57779278=
12fd9cd4d13da2fa4c
> =
commons-validator-1.11.0-bin.zip=3D277e102914059e5d122e95adfd28a8bb39b4dc6=
e9f1da99eae401524a2bcde3d6925f09596373e679f2b7d1317de5d6281022a0a19ffb5622=
3fee3b999cab737
> =
commons-validator-1.11.0-bom.json=3Df2240856cf00d531de0e8ef684b133e6562b76=
4b6db9a1a8f8a7377cf0bdcb096bceaa53489712ede2424c00931b51cc7a32d1b3d1bcfeb7=
ff25959c40e786c0
> =
commons-validator-1.11.0-bom.xml=3Db5435709e7cb85e601dd0753f53f383448bd436=
2905b04fde70166caf461901749ad7abfa5160ccab0b753c27de5d888d779b7dd5405600d4=
f0ab8348200441a
> =
commons-validator-1.11.0-javadoc.jar=3D8bcb11edea01ed047959022917e7c378479=
8310bc28be15ca83beebfa7d15423b9c211206cce00f8e91f4036a1b4dcb5e463a35774a7d=
95b4ee4446ca0e89e75
> =
commons-validator-1.11.0-sources.jar=3D15b1fdde20340a92457b38cf0cfc48813bf=
b7612dc1cb6b26fa3b006d2a710c5ef4046bf029bb3e05cefbf7c62800c21e79545d0b3c77=
c5e266a0edab8f040ce
> =
commons-validator-1.11.0-src.tar.gz=3D3eae75d9800d420168b00cdf0c8bcc0287d1=
1bf501cbe59175147bc5115a2381e256863d5c5a8820b303bc87168fc9b474302948708c90=
eaa6769c4bf55bb302
> =
commons-validator-1.11.0-src.zip=3Dad786ca8a447e81287b9f2590cebb5667842948=
9aa390cfe8f45424d2fa74ac452992c1c3fdbeb2c7e90482b3ca5383386c24bec3d6a4b1b9=
2440cfa42cf1a7e
> =
commons-validator-1.11.0-test-sources.jar=3Dd154d31c8936671a69a52505d80661=
8b52096590ae3a8065f20b769608113c5d851756df87853e89e284a7062c3cffbd86eaa7a2=
a6611fd7e85b697e9e4b2f88
> =
commons-validator-1.11.0-tests.jar=3D71f495868b2580add618bfd51785965090537=
4e404e00b9778456bf6a1c9143427c92f8c58d3a3d34d24bf0370f86c577b101cc3cf42fe4=
59dd3aecf88b96840
> =
commons-validator_commons-validator-1.11.0.spdx.json=3Dd9bad643608fc459119=
37df892dd9a8f0afe135c116352b4cefaa33187b9c3ce422dd8807aa008bc126af02457c3b=
847df7fa9a0583a13c293dc1470097069f5
>=20
>=20
>=20
> I have tested this with 'mvn' and 'mvn clean install site' using:
>=20
> openjdk version "27-ea" 2026-09-15
> OpenJDK Runtime Environment (build 27-ea+25-2247)
> OpenJDK 64-Bit Server VM (build 27-ea+25-2247, mixed mode, sharing)
>=20
> Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5)
> Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec
> Java version: 27-ea, vendor: Oracle Corporation, runtime:
> /Users/garygregory/java/jdk-27.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "26.5.2", arch: "aarch64", family: "mac"
>=20
> Darwin ****.local 25.5.0 Darwin Kernel Version 25.5.0: Tue Jun  9
> 22:28:34 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6041 arm64
>=20
> Docker version 29.4.3, build 055a478
>=20
>=20
> Details of changes since 1.10.1 are in the release notes:
>    =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/RELEAS=
E-NOTES.txt
>    =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/site/c=
hanges.html
>=20
> Site:
>    =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/site/i=
ndex.html
>    (Note some *relative* links are broken and the 1.11.0 directories
> are not yet created - these will be OK once the site is deployed.)
>=20
> JApiCmp Report (compared to 1.10.1):
>    =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/site/j=
apicmp.html
>=20
> RAT Report:
>    =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/site/r=
at-report.html
>=20
> KEYS:
>  https://downloads.apache.org/commons/KEYS
>=20
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
>=20
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
>=20
> Thank you,
>=20
> Gary Gregory,
> Release Manager (using key 530AA5F25C25011F)
>=20
> The following is intended as a helper and refresher for reviewers.
>=20
> Validating a release candidate
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> These guidelines are NOT complete.
>=20
> Requirements: Git, Java, and Maven.
>=20
> You can validate a release from a release candidate (RC) tag as =
follows.
>=20
> 1a) Download and decompress the source archive from:
>=20
> =
https://dist.apache.org/repos/dist/dev/commons/validator/1.11.0-RC1/source=

>=20
> 1b) Check out the RC tag from git (optional)
>=20
> This is optional,  as a reviewer must at least check source =
distributions.
>=20
> git clone https://gitbox.apache.org/repos/asf/commons-validator.git
> --branch commons-validator-1.11.0-RC1 commons-validator-1.11.0-RC1
> cd commons-validator-1.11.0-RC1
>=20
> 2) Checking the build
>=20
> All components should include a default Maven goal, such that you can
> run 'mvn' from the command line by itself.
>=20
> 2) Check Apache licenses
>=20
> This step is not required if the site includes a RAT report page,
> which you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
>=20
> mvn apache-rat:check
>=20
> 3) Check binary compatibility
>=20
> This step is not required if the site includes a JApiCmp report page,
> which you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
>=20
> mvn verify -DskipTests -P japicmp japicmp:cmp
>=20
> 4) Build the package
>=20
> This check should be included in the default Maven build, but you can
> check it with:
>=20
> mvn -V clean package
>=20
> You can record the Maven and Java version produced by -V in your VOTE =
reply.
> To gather OS information from a command line:
> Windows: ver
> Linux: uname -a
>=20
> 4b) Check reproducibility
>=20
> To check that a build is reproducible, run:
>=20
> mvn clean verify artifact:compare -DskipTests
> =
-Dreference.repo=3Dhttps://repository.apache.org/content/repositories/stag=
ing/
> '-Dbuildinfo.ignore=3D*/*.spdx.json'
>=20
> Note that this excludes SPDX files from the check.
>=20
> 5) Build the site for a single module project
>=20
> Note: Some plugins require the components to be installed instead of =
packaged.
>=20
> mvn site
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
>=20
> -the end-
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>=20