We have fixed a few bugs and added enhancements since the release of
Apache Commons Parent 101, so I would like to release Apache Commons
Parent 102.
Apache Commons Parent 102 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/102-RC1 (svn
revision 85033)
The Git tag commons-parent-102-RC1 commit for this RC is
30bfa34fc39800d29b58883eb2a489d9732c46f7, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=30bfa34fc39800d29b58883eb2a489d9732c46f7
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-102-RC1 commons-parent-102-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1947/org/apache/commons/commons-parent/102/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Jun 07 14:19:53 UTC 2026
commons-parent-102-bom.json=2618eac8da826709bb72eb5b0d481c9c8f86437dd5c978bba06f3999bc01a0a661c2d1459d099afa25c88817865c93f7530d9da5607f4ab099b5d71848bcb2c0
commons-parent-102-bom.xml=ee271ecd00d526844e9d0ecb422e31717c369b8a911dccc314039dd8e3391ecbd87a72e15a17a65364529d43de268a9b59a13ccffd56d9aaeaf8e63892d12268
commons-parent-102-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-102-src.tar.gz=518f704399d4f2afc3ebe99218e093387141e4b21fe223897cc90572fde720e247cb58f9d5a19f2341995fff39a690a3fe611ce49aec2c9186cd4667ad11197e
commons-parent-102-src.zip=227cfe4f4cff240734309c656cf0a762135a76496fda340d0033d2c7e6c5f1e6fcfabc771aeb8cf480673232d20752ebc56ef54de56e59c12d719c6a2a72910d
org.apache.commons_commons-parent-102.spdx.json=1cb431227c702c9a9931f8767fe833be8faefae0af023867a22227f9e7fc45786150b3d94fc28a91c10faffe9f7616e347a0733854021b4ebc4cce9e8dbf0cae
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "25.0.3" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 25.0.3)
OpenJDK 64-Bit Server VM Homebrew (build 25.0.3, mixed mode, sharing)
Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5)
Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec
Java version: 25.0.3, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@25/25.0.3/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "26.5.1", arch: "aarch64", family: "mac"
Darwin Garys-MacBook-Pro.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 101 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/102-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/102-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/102-RC1/site/index.html
(Note some *relative* links are broken and the 102 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/102-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/102-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-102-RC1 commons-parent-102-RC1
cd commons-parent-102-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]
