[VOTE] Release Apache Commons Configuration 2.15.0 based on RC2
We have fixed a few bugs and added enhancements since the release of
Apache Commons Configuration 2.14.0, so I would like to release Apache
Commons Configuration 2.15.0.
Apache Commons Configuration 2.15.0 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2
(svn revision 84480)
The Git tag commons-configuration-2.15.0-RC2 commit for this RC is
26d8bc8c397296983800da80ef1277dbdb5700e4, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=26d8bc8c397296983800da80ef1277dbdb5700e4
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-configuration.git
--branch commons-configuration-2.15.0-RC2
commons-configuration-2.15.0-RC2
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1936/org/apache/commons/commons-configuration2/2.15.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Tue May 12 11:56:24 UTC 2026
commons-configuration2-2.15.0-bin.tar.gz=519442b9e9f970e6f63b093a478a63325782d272e5cf1795bfa873ca279428dddd3713195ae0ec9625371c5eb584d260ae617edab4dca8910f6e575346555657
commons-configuration2-2.15.0-bin.zip=c75133cc2d652dd9892637fd6674845e4bf8a54654d99a76249f38226faec9485aee99f091439a56850019e333390c2097de117c0f7f6856ebb624f022c69254
commons-configuration2-2.15.0-bom.json=71e7393b4253b462c417601528d660139074cfe1d1b75c3f3506521778a7f881d3c6feb1cbd06d8b285fac728a77c396ec873de1fa5f83f2315036871514c219
commons-configuration2-2.15.0-bom.xml=d5b6ad142fb9f46e43079f67ed47cb46e4898a10e9c236a29de7e57fe9395e228ba38a4ee47cfdf3917423f936153793588296d55ead2dce995636fb1071730c
commons-configuration2-2.15.0-javadoc.jar=cbb32b8797c441a8f5e5b10acd976cf30613c2391c1738cdedc24a09fb345929f092c6aef760106b32596e028f774e8a6426e61b9a8ecd518b91574dce7d473e
commons-configuration2-2.15.0-sources.jar=e1d7dbb59cab77f664f77b280ad9bd23449d1d024e13f18ea0358a61bc66a9eca88e7e0ccfda9d709b86132de9a442f93589c745161440e1329d327568a1984b
commons-configuration2-2.15.0-src.tar.gz=c838bbc02c7c832add923e77ad7a0e4b95add490c34a14ac573bfe959f6ecd8efdaac6d3fd5257a1a3865cf55bfee870a4c98fb2aa818b5880ee63c868832a68
commons-configuration2-2.15.0-src.zip=46e2ead9df4f5e1aca51863772cd35d163e339b7d1aa78e2a7dff56c27129fa630c0dd53465140ca214d5179f695be0da2e9778cca5711ff3cf966ead5933336
commons-configuration2-2.15.0-test-sources.jar=2b4e8bdf8111787bf2fd7f36f14cecb1898ac4ade3e5447a83cfe7d2aaab5accad8a3c47b76ae840e317adc5bf91fcf3549e06d28a89e0cbeffe9bdf686c90d5
commons-configuration2-2.15.0-tests.jar=6eb3610528c7062e9628181fd9207d74466117d34f0aae02b5b9f654094c97ddbbef57541a39635cbb51b39003ac4f1b091446bfe876bbc0be9b48ae4b3cab16
org.apache.commons_commons-configuration2-2.15.0.spdx.json=50f23ef711a9d6974d70609617d6aa657788976d7eab3e517a87f2464c3120846526e4e2cd7b1f2bbc91f254b9f17ad69962592c85e869f7d08c08652587d275
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.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"
Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64
Docker version 29.4.2, build 055a478
Details of changes since 2.14.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2/site/index.html
(Note some *relative* links are broken and the 2.15.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.14.0):
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC2/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 24 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.0-RC2/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.0-RC2
commons-configuration-2.15.0-RC2
cd commons-configuration-2.15.0-RC2
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]
