Clean simple builds on all aspects 11 - 25. Signatures check out, site looks good, reports look good. Go
+1 > On May 11, 2026, at 3:33 PM, Gary Gregory <[email protected]> wrote: > > 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 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC1 > (svn revision 84468) > > The Git tag commons-configuration-2.15.0-RC1 commit for this RC is > ece3388fde750504bb87aacdb6231b495a671625, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=ece3388fde750504bb87aacdb6231b495a671625 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch commons-configuration-2.15.0-RC1 > commons-configuration-2.15.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1935/org/apache/commons/commons-configuration2/2.15.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon May 11 19:23:06 UTC 2026 > commons-configuration2-2.15.0-bin.tar.gz=d57958f05d0a0d0f0c19f8595152ef0141e333dbe501b86e2506e42a6841a81e400cb8f8001a348ef3f7826704e0f2bfaf91b2b960e46b053fef3524515117b1 > commons-configuration2-2.15.0-bin.zip=f98663eedc3ca6cece9d9b6f232b68663b94e7e1cf43ec68a7335edf721d59702b0852a315d7fde72fc106dd14364627fa10845fe7a7aecb2caade774774291d > commons-configuration2-2.15.0-bom.json=71e7393b4253b462c417601528d660139074cfe1d1b75c3f3506521778a7f881d3c6feb1cbd06d8b285fac728a77c396ec873de1fa5f83f2315036871514c219 > commons-configuration2-2.15.0-bom.xml=d5b6ad142fb9f46e43079f67ed47cb46e4898a10e9c236a29de7e57fe9395e228ba38a4ee47cfdf3917423f936153793588296d55ead2dce995636fb1071730c > commons-configuration2-2.15.0-javadoc.jar=9638682d72d6aa3cd5d7e1ae81fdc49e436a9c23c65f4e8c9a39e80ff574ce3631a020a64809ab9d57fc62bf99e982ddaf540dba86586df2f3374162c7dfd012 > commons-configuration2-2.15.0-sources.jar=287f9418f8df63bc07c9b3ccd9ac4e6f2873b7100f740f75a601928680e8cb7447a6a2a3b36171e0544dea47d9a27604fb852a15afeab5c23d785abaa0254c0d > commons-configuration2-2.15.0-src.tar.gz=1ed78d7401c7b26fef846dc03322f3d3c1c2a680d0534abbc21a926e9af682bd87ef478434137e8de07e77c0f9972a394617333aee11f7eefd8a1e34454092c6 > commons-configuration2-2.15.0-src.zip=82a70e232b7f19bbcc88701fceac2355a778333bc63b337cdb966b47f98131196f21b57564beec1500a7d989569b62ec4d857e8abff0dbd0071f63ed86953379 > commons-configuration2-2.15.0-test-sources.jar=76b9b7a5a21c592f05c6bb2acf9257d9a89d8451f2713f7b39d2dbad0911e38296fdac90269b8019b4d8248e8d6e50be466ca6147b2cb73372a1db539c44adaf > commons-configuration2-2.15.0-tests.jar=b798f2d5e396a27463135034136033cfb75904aa57a05c2907780eb0bf190a150fe2257140d848c7eb089147f99e1bc18f74633aedb3e40ca8addaa978d31681 > org.apache.commons_commons-configuration2-2.15.0.spdx.json=6f4e0a69f2a556f91c063247e27dc410e6e1a58e011fec9fb4cdfeeb153b8542f0bbce2a946622e0a1420d9f2fe41cee80de03045c5cded2a6ac4f70f18e7733 > > > > 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 Garys-MacBook-Pro.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-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-RC1/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-RC1/site/japicmp.html > > *** > Note that the above report notes several errors. > These are considered OK for the reasons stated below. > These exceptions are also noted in the Changes and Release Notes. > > Errors reported: > - methods added to interface: OK because that does not affect > binary compatibility. > - etc. > *** > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.0-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 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-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.0-RC1 > commons-configuration-2.15.0-RC1 > cd commons-configuration-2.15.0-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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
