Installed from the source tar. Built Numbers, Statistics using:
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) Maven home: /Users/ah403/mvn/mvn Java version: 21.0.11, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "26.4.1", arch: "aarch64", family: "mac" Built Collections using: Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) Maven home: /Users/ah403/mvn/mvn Java version: 17.0.19, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "26.4.1", arch: "aarch64", family: "mac" Verified the SHA 512 for the source archives. Ignored the checksums for the other files. Checked the pom vs 99. All changes in the release notes are correct. There is also a change to Mokito dependency (to pom type with import scope) not documented. The old scope was test but in a managed dependency so downstream projects would redeclare anyway. Not sure if this is important enough to include in release notes anyway. +1 Alex On Mon, 11 May 2026 at 12:41, Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since the release of > Apache Commons Parent 99, so I would like to release Apache Commons > Parent 100. > > Apache Commons Parent 100 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/parent/100-RC1 (svn > revision 84448) > > The Git tag commons-parent-100-RC1 commit for this RC is > 718f00cba9d5e0463a16d5957cd81c5e851d91b2, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=718f00cba9d5e0463a16d5957cd81c5e851d91b2 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > --branch commons-parent-100-RC1 commons-parent-100-RC1 > > Maven artifacts are here: > https://repository.apache.org/content/repositories/orgapachecommons-1934/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon May 11 11:33:05 UTC 2026 > commons-parent-100-bom.json=66d8e0fac9775181bd2848b57f5026334a255901b1568cf09bf6dcc138bfc44188662e740124387765143cd87258909bc422166e34104feb71c13c995a7b24ba > commons-parent-100-bom.xml=ca75124a8c6485671695a976e70287647eea9ae7b0280eef67fc818ebcfd3fce018a68ff7b6c044d66609aa533257e8dfdc71052994a4bf76a0dab47df0713e8 > commons-parent-100-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a > commons-parent-100-src.tar.gz=595d764d0b6e343de3b8cb0e3eabdce4454f54873b910c4076b797a422fe6e0ab80409f6eca937da86d669af70c4658341a9f01c4c8f7665ce4f1495178c8be3 > commons-parent-100-src.zip=6f209b62b5e1e7117952e828603b9b4caab73d34b82b74e2f5b9f36ac48f2b4d515c289b21c4da60fb20b4ad211ea2ffc860f8bb18c0e63381a0a50202718724 > org.apache.commons_commons-parent-100.spdx.json=20c47a62949f3391d74ab3648aaf24bf7104ab2b921e2ebc612fcf3a5a13c3cbd510432de56d6b3b03efa2d5dca0768f5a80dd4742e425af75780a510e6ed79f > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.11" 2026-04-21 > OpenJDK Runtime Environment Homebrew (build 21.0.11) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.11, mixed mode, sharing) > > Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349) > Maven home: /opt/homebrew/Cellar/maven/3.9.15/libexec > Java version: 21.0.11, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.4.1", arch: "aarch64", family: "mac" > > Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19 > 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64 > > Docker version 29.4.2, build 055a478 > > > Details of changes since 99 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/parent/100-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/parent/100-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/parent/100-RC1/site/index.html > (Note some *relative* links are broken and the 100 directories are > not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 99): There is no such report for Parent > since it contains no Java code. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/parent/100-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/parent/100-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > --branch commons-parent-100-RC1 commons-parent-100-RC1 > cd commons-parent-100-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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
