We have fixed a few bugs and added enhancements since the release of
Apache Commons Parent 100, so I would like to release Apache Commons
Parent 101.
Apache Commons Parent 101 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/101-RC1 (svn
revision 84849)
The Git tag commons-parent-101-RC1 commit for this RC is
2765a161d05f5a706f7f19e4ea74282d3e891adc, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=2765a161d05f5a706f7f19e4ea74282d3e891adc
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-101-RC1 commons-parent-101-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1945/org/apache/commons/commons-parent/101/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat May 30 12:37:20 UTC 2026
commons-parent-101-bom.json=677d2027a05f7fe4eafdd24ca7c77bfe7e68b6cd6f44f6bcb5b74073eb1185c479d511f5e547c062e70b338cb696ab847769a61bec0472c122dcabb54f829875
commons-parent-101-bom.xml=0c1ade01fd4667b26077717bf63f738bff3e0cec22b928ac44a261f77af67abc40b27de78cec158430b9cc4466865f01c655be4c0920458c39dee39012ef9057
commons-parent-101-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-101-src.tar.gz=f4a9040c2ce8f1d1f2d8845ccfd3ecd2552b9d946c557f9a353263872c00c0313072a7da50d689db984c9e231dcad57416f6c18081407f5a06e67b485a42a262
commons-parent-101-src.zip=d35eec7994dcf3ff6ced65da3e85e60886c257ac9bfa3051620c1ee95c9742adedeb3afd274c3859825818cf425088f99ea7135801947e7fd4b7cd68a7078e3f
org.apache.commons_commons-parent-101.spdx.json=fd209dbe15f0fabc535e8f30603e0566d7e281cbbd3c5182cf4680d8bc51a68445a42747e2b823a9f5aba75222083f9e0cd4cd2ec7112bdb429a341f893b5b7e
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.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5)
Maven home: /opt/homebrew/Cellar/maven/3.9.16/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.5", arch: "aarch64", family: "mac"
Darwin ****.local 25.5.0 Darwin Kernel Version 25.5.0: Mon Apr 27
20:41:15 PDT 2026; root:xnu-12377.121.6~2/RELEASE_ARM64_T6041 arm64
Docker version 29.4.3, build 055a478
Details of changes since 100 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/101-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/101-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/101-RC1/site/index.html
(Note some *relative* links are broken and the 101 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/101-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/101-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-101-RC1 commons-parent-101-RC1
cd commons-parent-101-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]
