We have fixed a few bugs and added enhancements since the release of
Apache Commons Parent 102, so I would like to release Apache Commons
Parent 103.
Apache Commons Parent 103 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/103-RC1 (svn
revision 86073)
The Git tag commons-parent-103-RC1 commit for this RC is
864a386cce50e6c86fdde471338d34a8f62ae0bc, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=864a386cce50e6c86fdde471338d34a8f62ae0bc
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-103-RC1 commons-parent-103-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1953/org/apache/commons/commons-parent/103/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Jul 18 21:23:11 UTC 2026
commons-parent-103-bom.json=77b66cba25fcbad01e38a7c87220dec2bb7a16499cc1cbbddf862de57c7199daf252b3c5ce2254f41b597f4d70c744eb669d5eaba3c3b3666474ba4b377c5cbe
commons-parent-103-bom.xml=67e329b854d6c9f5c01a59621e757051d4c62e4df6c2e3e511732b31c0f4e67040d55d4f694822fa2037c2bf19506b524e611fc7fdec715a4c4e0a8f750ce0f4
commons-parent-103-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-103-src.tar.gz=403e44b3161be93fbaf18ce8daa520affab1346b19e12c75a37c109338f2b3f1dd71851b2824b36fca6a01939c51d95399672f633412c638b2d5baff606dbe2d
commons-parent-103-src.zip=db07c1f60bc9f5ce38e7bc7c832e67f1cc199ccafd51bd01cdc57f4c5592c1ac17a7b59febe23bfc92e28081c2165659302e6a7a78a333967fc6f22669243be8
org.apache.commons_commons-parent-103.spdx.json=9fb9f23be5c8582e3205edea35a700fc112ecc1ac0bca66c32eb85ce49079c2167f80adde338f68894064de6924dcd2bd9fbb9bdd1be42c3c273501ce4369fde
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.2", arch: "aarch64", family: "mac"
Darwin Garys-MacBook-Pro.local 25.5.0 Darwin Kernel Version 25.5.0:
Tue Jun 9 22:28:34 PDT 2026;
root:xnu-12377.121.10~1/RELEASE_ARM64_T6041 arm64
Docker version 29.4.3, build 055a478
Details of changes since 102 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/103-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/103-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/103-RC1/site/index.html
(Note some *relative* links are broken and the 103 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/103-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/103-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-103-RC1 commons-parent-103-RC1
cd commons-parent-103-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]
