By users' request, we have fixed 1 bug since the release of Apache
Commons Configuration 2.15.0, so I would like to release Apache
Commons Configuration 2.15.1.
Apache Commons Configuration 2.15.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC1
(svn revision 84600)
The Git tag commons-configuration-2.15.1-RC1 commit for this RC is
5db07bc7da76bb9688b104f54798966f3e5d31b6, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=5db07bc7da76bb9688b104f54798966f3e5d31b6
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-configuration.git
--branch commons-configuration-2.15.1-RC1
commons-configuration-2.15.1-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1937/org/apache/commons/commons-configuration2/2.15.1/
These are the artifacts and their hashes:
#Release SHA-512s
#Mon May 18 16:57:44 UTC 2026
commons-configuration2-2.15.1-bin.tar.gz=579381ad8077eb381be4b9fa778a0c71188a40693b85544da645a1a2a56aca4db1fcf4de85bd09e89edac443b44d64ce9037e57a74b91b43759919786f6834f8
commons-configuration2-2.15.1-bin.zip=b1ffc8044f9730c78dc4adf565e843701e1e97a0efb1313dd4b4554211f0aff4619380dc6bca57bf3caaeb30bcc040b454a5c725dc57959066320192bad0ed2e
commons-configuration2-2.15.1-bom.json=9fc27a1427f7e00995469cd84e9255a3352be01502bfc7f62ca030bb918bc32aeda9ed1bbf6bb916e6ae764683f5446d9721f746d9e1fe1473a2df7babaf6ce3
commons-configuration2-2.15.1-bom.xml=a3a2e0da3df209672cb93d794afe67ba01cf4e5247c75075dc6c14aefd336f2079d387e6e8fa70ea67e280485236ea3d42673c0b8f31df21a1cdf13c586acefe
commons-configuration2-2.15.1-javadoc.jar=66cf17f9f8d9a6d12e293d7bec946714cc8ef9b5ef26b303c75c8169b3d317d9f663f97dbcf12a8993692b6153662b4afc638b6c6b43e602dc77fa3381dff867
commons-configuration2-2.15.1-sources.jar=2a9384d77f72cceecaf7049d55a655f30cd363e3598ef38af0a7fdbe320eb8c6cc98f15fe38740b82f15da0b3bb1d9326fe89fe6c96945f85073e6961d5bbc1f
commons-configuration2-2.15.1-src.tar.gz=34532b5a393c6bc26eb5ee959419f18b096b2dbfbb67046bbe62a6d92a61d2bfb9b56787a12b10f91325b564664223d74c8132da5aaaa5410c10d91c8461b606
commons-configuration2-2.15.1-src.zip=07144b3eb5352b63dccad29099b98de32b6c90d5958408511b691fcee0e365bcdfdecbff2ca880e8a1f2478673a44d9f0137b2813b97db3d1b6fe96c08d5e721
commons-configuration2-2.15.1-test-sources.jar=ab4234974dcb272341f0f62e555057a6f44bfca3594542de7c4c7dd524074a31810c9a3617a65f0b29451d0beb79a05318cc8fc90f6f4c4e9e99d86b94196939
commons-configuration2-2.15.1-tests.jar=4fef68ec59f2cfb8e14a12e19dd6595be8a5513df5cb3d3e5259b33eddb244c57aa825e567d0052e934b793ac795c40ed2fbc6d417aa18b95548826071e851af
org.apache.commons_commons-configuration2-2.15.1.spdx.json=0d58fb0fef4d4a7b0a1d7917cdf985a5ba619b7c72c987262e0e6e78c5d387e35110cd78a7d64d1d148fdebc56232ba5e65b8ea0839fe6728c7d2680423d89a5
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 **** 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 2.15.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC1/site/index.html
(Note some *relative* links are broken and the 2.15.1 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.15.0):
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-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/configuration/2.15.1-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-configuration.git
--branch commons-configuration-2.15.1-RC1
commons-configuration-2.15.1-RC1
cd commons-configuration-2.15.1-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]
