+1 All checks out….and again Thank you Gary!!
> On Jul 6, 2025, at 8:16 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Validator 1.9.0 was released, so I would like to release Apache > Commons Validator 1.10.0. > > Apache Commons Validator 1.10.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-RC1 > (svn revision 77970) > > The Git tag commons-validator-1.10.0-RC1 commit for this RC is > 8bb55004a4a00c2bd58d234aa88680f06fc26233 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-validator.git;a=commit;h=8bb55004a4a00c2bd58d234aa88680f06fc26233 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-validator.git > --branch commons-validator-1.10.0-RC1 commons-validator-1.10.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1844/commons-validator/commons-validator/1.10.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Jul 06 12:11:36 UTC 2025 > commons-validator-1.10.0-bin.tar.gz=1a93da96f4cc621cb61bc7039325795366d713d9b07737e885910392142d03c5fb00cf53ac22493c9d73afe306dd02756d8d4db7b71fe010bc75eb66918c3da1 > commons-validator-1.10.0-bin.zip=1a6c7fb83bc60fb55490885f4ee40e1addf414733c308ac39c95683e75649387771e49eb7619400a8a06ddf8d07e0e0a86bfaf73f6accc34d8df5d177b63d4d0 > commons-validator-1.10.0-bom.json=5ec42dfe81fa4681dd85d8c2e60d91cba0aafa4b51748d248285a1d8b6b48b9310bce3895bd3aa16fc7249708fa9829b1c40681d2b64ccc8175dd63770b8620e > commons-validator-1.10.0-bom.xml=8ced150aaa35fd03194e0f1c3d0e1faa67ce4a253b4c5df4d3d204a9be6c059b0b6bea5ca11104d6394604ec4cd454e273d7c289302442c8cb987598c45df2d8 > commons-validator-1.10.0-javadoc.jar=445a7867280ce84ee042cca5142c4833ddac713737a6209066be39b899879b0b311fc384d0f0849a4624d5a4df0109e5604603760001c0dbe51e2c541406c8d3 > commons-validator-1.10.0-sources.jar=40781fc45cf3ba1e8b81197a4c3a2bad0d96922571ae0af01b9dfeaabc4ab83f35fa93b9b2c0cc59d9f5e164fd500bac6ccdca9f998279d803fc9e8eded62b1a > commons-validator-1.10.0-src.tar.gz=4a89e4b59c6cb255fbb827ec6b8561be12a79d9c1031be6e2fdd9416c4e7aef1917a2578a0c3265562c379081ce9b9c66d93a86d8eb440164c839de00ce15ab6 > commons-validator-1.10.0-src.zip=6926a308b28f4bc3816e819baf697ecc67d615734bbe903ea7cd3b416cd2f706a9914c980812acd0a03f89298bf12e99e8578cd87d597c755938eed34d6045a1 > commons-validator-1.10.0-test-sources.jar=0f3c5b795d07bc7a14df253c93ae5b6dc7b64bf94231b21739f2afadd809cf650aee79de39f7a6f35c3b0ac2723d16e5adf9f809410337a2b5de1ed3fffaed08 > commons-validator-1.10.0-tests.jar=75d495747121e44107ee8ff2fef56847cabfac49141de6eed2836ed4e886725f31fa4de53f06373934dcdf75693d5b6f7f5d9a0e01421bec0a844695bab8679f > commons-validator_commons-validator-1.10.0.spdx.json=4cec04669ec34a008d730fbb4cd85e05e2115d22151a1e7648cd7d32e66a4211be5c60b4f07544845011efb9e2d34bf18ec286ab4fcb49f82a8f4157c141b794 > > > I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "21.0.7" 2025-04-15 > OpenJDK Runtime Environment Homebrew (build 21.0.7) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.7, mixed mode, sharing) > > Apache Maven 3.9.10 (5f519b97e944483d878815739f519b2eade0a91d) > Maven home: /opt/homebrew/Cellar/maven/3.9.10/libexec > Java version: 21.0.7, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.7/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac" > > Darwin ****.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 > 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 28.3.0, build 38b7060 > > > Details of changes since 1.9.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-RC1/site/index.html > (note some *relative* links are broken and the 1.10.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.9.0): > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.10.0-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 86fdc7e2a11262cb) > > 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.0-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 commons-validator-1.10.0-RC1 commons-validator-1.10.0-RC1 > cd commons-validator-1.10.0-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: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
