My +1 Gary
On Fri, Apr 3, 2026 at 9:45 AM Gary Gregory <[email protected]> wrote: > > This is a small feature release adding support for loading XML DOM > Element into an XML configuration from a larger parent document. > > We have fixed a few bugs and added enhancements since the release of > Apache Commons Configuration 2.13.0, so I would like to release Apache > Commons Configuration 2.14.0. > > Apache Commons Configuration 2.14.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.0-RC1 > (svn revision 83599) > > The Git tag commons-configuration-2.14.0-RC1 commit for this RC is > c2c5ff2d7cf14a540671764323847750c577620a, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=c2c5ff2d7cf14a540671764323847750c577620a > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch commons-configuration-2.14.0-RC1 > commons-configuration-2.14.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1925/org/apache/commons/commons-configuration2/2.14.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Apr 03 13:35:03 UTC 2026 > commons-configuration2-2.14.0-bin.tar.gz=27b854e28d7a3cab8bdbce8a70b94123441b6dea578ba96a9a7200d875635037f07d345d30d3cda77305056688bbd2fbeda00081494f6bf674bfb2cf38b497bd > commons-configuration2-2.14.0-bin.zip=fcbaed9dbb613afaafe7d1f9e9b1d6566465164ba7b8eed3bea32fc7e3358d37a6a7f45fdb8205834441b0dde1888149a039982fea86c0f321573080580a0bbb > commons-configuration2-2.14.0-bom.json=d2db5dc86d704666b629c1ae62586863a8349438b581eeda8c459d9b90226fe46828daedd8fd4093a54c5ed2db2efe874cc0ab0f13a59f9dafd11fa1da790785 > commons-configuration2-2.14.0-bom.xml=b388d1c45f32676a4f0b470330b2a141260454811d01589e68044e59c1b62f0777354840d58e2ed440b7071738a07190e89cc395af6c58ac29c4663b501d094e > commons-configuration2-2.14.0-javadoc.jar=e8d36202769c512b316885bf2d5eebd514b4169faacdc01d55740bfa8403c94febd826ae818fcd7bbdd35f541f6eee3c3d33f303b59a8a3229ff90effbcde007 > commons-configuration2-2.14.0-sources.jar=746bf5cc74f78ba4b1efc9d734e6810f9ff404c7d4cc86260c728f954aed31719b25bae41ccc5a62b455444f1155856e0e5a6c09f3de44e3452e70aabc8c0bef > commons-configuration2-2.14.0-src.tar.gz=b1d372ff5f37f068653d0a9b5f4fef9cab98a1aef515907cfb3eabfe1ae2c8d0ad51f32a12dd18651a4e7c43193a24ab15807db7d3acc2a89ef662b78d380fa3 > commons-configuration2-2.14.0-src.zip=6d34d48b77707d704447769bb5a7ba7603fe51adaa953f7c419788d44e3d9090de7f690a05f86ae7948b811cb07570bb6b0f1bef8d4056c2b5cc108ae54d405b > commons-configuration2-2.14.0-test-sources.jar=e5bf77de04b8d4a075b8c1314ae1cb0a84537c7af970f1500f2804fa61a04d5a6254930df72cfa98fe65d542d92ea3fbcb0f81f8db267212965b8fb2fcbb93ce > commons-configuration2-2.14.0-tests.jar=5a8b9417d8a808144f17b8eb444518e7c83ba97d533db69408c3ecf94b6ab5ace97d3e2ef9c6556033d4ab969c83b1648b8d6d3ca9bf7e4734f5d372373a3a2d > org.apache.commons_commons-configuration2-2.14.0.spdx.json=08eee23800af071d43c47cb9d908c6a6dd02ddab2d6f60c64f94415a590ff201623be4e2d81dcbd9db3461987e4ba24560400e2a8c71b0dd151742d3bc462dbe > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.10" 2026-01-20 > OpenJDK Runtime Environment Homebrew (build 21.0.10) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.10, mixed mode, sharing) > > Apache Maven 3.9.14 (996c630dbc656c76214ce58821dcc58be960875b) > Maven home: /opt/homebrew/Cellar/maven/3.9.14/libexec > Java version: 21.0.10, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.10/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.4", 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.2.1, build a5c7197 > > > Details of changes since 2.13.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.0-RC1/site/index.html > (Note some *relative* links are broken and the 2.14.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.13.0): > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.14.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 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.14.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.14.0-RC1 > commons-configuration-2.14.0-RC1 > cd commons-configuration-2.14.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]
