+1 Sigs and hashes are good. Changes look good. Reports are clean, except cpd, whose complaints look mostly spurious. Builds clean on openjdk versions 1.8.0_462, 11.0.28, 17.0.16, 21.0.8, 25 All under maven 3.8.7 on Ubuntu 24.04.3.
Thanks for the RM Phil On Fri, Nov 14, 2025 at 8:58 AM Gary Gregory <[email protected]> wrote: > We have fixed one NullPointerException bug since Apache Commons > Validator 1.10.0 was released, so I would like to release Apache > Commons Validator 1.10.1. > > Apache Commons Validator 1.10.1 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1 > (svn revision 80713) > > The Git tag commons-validator-1.10.1-RC1 commit for this RC is > 0290614da63ac0b6983ad18005d07b597f6db25d, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-validator.git;a=commit;h=0290614da63ac0b6983ad18005d07b597f6db25d > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-validator.git > --branch > <https://gitbox.apache.org/repos/asf/commons-validator.git--branch> > commons-validator-1.10.1-RC1 commons-validator-1.10.1-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1880/commons-validator/commons-validator/1.10.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Nov 14 15:42:01 UTC 2025 > > commons-validator-1.10.1-bin.tar.gz=fecbb780a60eb117affa11b5b0166ced3ea7c49cc04edb3720eaeea7aaa83206cbd56cc3b01819da7b52d73ffb1805d1bb314ff10efae9c34cd2eafb165dee48 > > commons-validator-1.10.1-bin.zip=e50321c229feaabe271e5ead0ebd37a017bae9dc72d3ddfb742faa7f87cff7d08a3b5a985c6e94066bfe7d5cdef29349148679f1ff98794ae40ea24090166769 > > commons-validator-1.10.1-bom.json=e8765f778818442d39015228591299000997d12fbaf69c65dadf68a68f983a10a54ff827f67f87b96821f65c388cc73c2316fa474dfd461ef2cb1073498a693a > > commons-validator-1.10.1-bom.xml=2e7d53cdb462b7ae516c0161a30cb0398f4349ca2f3e0e4c16437d6b929f7242158499aa8c8910dcf0e8449f116602dbd06284b85b2f5818b8808e1560cca2e1 > > commons-validator-1.10.1-javadoc.jar=9083cc1997463740dc0b9cffdc2f9985f3c6096b2cbd36fedc9339f99b3017a0b12ac591935313cacc08f282987eb501488a6db99ca65b8aaca9bdd2d2e85078 > > commons-validator-1.10.1-sources.jar=5a81fdc82bd0861ed71b25bc88328dfbd032325e8c2df563d5d3494908689c31993230efc0c0eeb9f8ce238b8064b1dd48e988184c9fc475804cf2d52b6ace7f > > commons-validator-1.10.1-src.tar.gz=df71f331962823229992022786299f1c4911cc79fdd6b983a1dbfba211b00c56fbc5b000c923f208813b6a95de5558286472f8e3cae0427a9e6725f2eb062be4 > > commons-validator-1.10.1-src.zip=1becf127b2b0b0a9e36ad2ee0d6e07be60479dc11a5f4abe72edb6c706d61b7ad724d3a12f9cd41d1cf69e894150693b87dd88e8f1245e1d57be8a7898ededb2 > > commons-validator-1.10.1-test-sources.jar=e06d55ca27e26ddd4fdfa56b5797072b5d738715e80e67f92230183372b78d1ae3f2619de24ca5ac22a45260d815d976752ecb788b8839122dc4bc7eb279c1bb > > commons-validator-1.10.1-tests.jar=21f16fcea11b982e1a5318f0fda30b9a3017a916962d0e50803082d08ff13ac7805288a70b7b668ceabedeea968a606d8674e557a16404446e395d32d2fa4aa0 > > commons-validator_commons-validator-1.10.1.spdx.json=ec5cec9b65953e40ce797d4391372b4dc32a5d8e6fff236b628d56f44b02871982742525cc131e3dc8824e17e5203779d80d7f203ea60c07507d52271809b352 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.9" 2025-10-21 > OpenJDK Runtime Environment Homebrew (build 21.0.9) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.9, mixed mode, sharing) > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > Java version: 21.0.9, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.9/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac" > > Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Wed > Oct 15 21:12:15 PDT 2025; > root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041 arm64 > > Docker version 28.4.0, build d8eb465 > > > Details of changes since 1.10.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/site/index.html > (note some *relative* links are broken and the 1.10.1 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.10.0): > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/site/rat-report.html > > KEYS: > https://downloads.apache.org/commons/KEYS > > Please review the release candidate and vote. > This vote will close no sooner than 72 hours from now. > > [ ] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... > > Thank you, > > Gary Gregory, > Release Manager (using key 530AA5F25C25011F) > > The following is intended as a helper and refresher for reviewers. > > Validating a release candidate > ============================== > > These guidelines are NOT complete. > > Requirements: Git, Java, and Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Download and decompress the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.1-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must check source distributions as a > minimum. > > git clone https://gitbox.apache.org/repos/asf/commons-validator.git > --branch > <https://gitbox.apache.org/repos/asf/commons-validator.git--branch> > commons-validator-1.10.1-RC1 commons-validator-1.10.1-RC1 > cd commons-validator-1.10.1-RC1 > > 2) Checking the build > > All components should include a default Maven goal, such that you can > run 'mvn' from the command line by itself. > > 2) Check Apache licenses > > 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: > > mvn apache-rat:check > > 3) Check binary compatibility > > 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: > > mvn verify -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > This check should be included in the default Maven build, but you can > check it with: > > mvn -V clean package > > 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 > > 4b) Check reproducibility > > To check that a build is reproducible, run: > > mvn clean verify artifact:compare -DskipTests > -Dreference.repo= > https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json' > > Note that this excludes SPDX files from the check. > > 5) Build the site for a single module project > > Note: Some plugins require the components to be installed instead of > packaged. > > mvn site > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > -the end- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
