We have bumped dependencies since Apache Commons Parent 90 was
released, so I would like to release Apache Commons Parent 91.
Apache Commons Parent 91 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/91-RC1 (svn
revision 80286)
The Git tag commons-parent-91-RC1 commit for this RC is
24d6986b39fa3eea012da94e92c9447558ebff59 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=24d6986b39fa3eea012da94e92c9447558ebff59
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-91-RC1 commons-parent-91-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1867/org/apache/commons/commons-parent/91/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Oct 25 12:42:17 UTC 2025
commons-parent-91-bom.json=c5c9ac197b0d8c05b84083625f8a26afc5371051d8c00afd2373a9394515e09819ca759b8a298753b39dbddbc9de5ed1b1aa8b3838503af5e4d67b16b9d7b082
commons-parent-91-bom.xml=4b3ec5ca5e4620e79dcd449b19bea0543abccbe758c4b4540526da380087060c0026d4a1defb8f092ccac1dcbe76e2d99c604eda1e8d334fdc2bbb9a0beefe96
commons-parent-91-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-91-src.tar.gz=74c049e82ae0a9ba40182f6eb065663714897b03f43bd346d512ebdde5f5bba4434e5d70e5b7863759ab938a15608ca910688c631363c0c27a25901016d08819
commons-parent-91-src.zip=dc36a39ed318cbb4ab6840e14041f68fc7a48e47ffe7a4ad72d817e4e5d0dd5db61ed3b29c2d63a1c4c393463dc53e95d61e0d7aba606b0e0a21e0412a708c91
org.apache.commons_commons-parent-91.spdx.json=2b73e30aefdc8b942b4223edb278c82586f16c9a92c844d001bc59b0dbd6dd04b17cb405f7ddf178218ffa62af152a618e0e8386e071305e3575e0e5ab8d190e
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "25" 2025-09-16
OpenJDK Runtime Environment Homebrew (build 25)
OpenJDK 64-Bit Server VM Homebrew (build 25, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 25, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk/25/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.7.1", arch: "aarch64", family: "mac"
Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Mon
Aug 11 21:15:09 PDT 2025;
root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6041 arm64
Docker version 28.4.0, build d8eb465
Details of changes since 90 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/91-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/91-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/91-RC1/site/index.html
(note some *relative* links are broken and the 91 directories are
not yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/parent/91-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/parent/91-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-parent.git
--branch commons-parent-91-RC1 commons-parent-91-RC1
cd commons-parent-91-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]
