commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject [VOTE] Release Apache Commons Configuration 2.6 based on RC1
Date Sat, 14 Sep 2019 01:23:51 GMT
We have fixed a few bugs and added some enhancements since Apache Commons
Configuration 2.5 was released, so I would like to release Apache Commons
Configuration 2.6.

Apache Commons Configuration 2.6 RC1 is available for review here:
(svn revision 35830)

The Git tag commons-configuration-2.6-RC1 commit for this RC is
32d6be96f6b101dfd18d21d79788980ee08e5965 which you can browse here:;a=commit;h=32d6be96f6b101dfd18d21d79788980ee08e5965
You may checkout this tag using:
    git clone
--branch commons-configuration-2.6-RC1 commons-configuration-2.6-RC1

Maven artifacts are here:

These are the artifacts and their hashes:

#Release SHA-512s
#Fri Sep 13 21:09:00 EDT 2019

I have tested this with

mvn -V -Prelease -Pjacoco -Ptest-deploy clean package site deploy


Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
Maven home: C:\Java\apache-maven-3.6.2\bin\..
Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Details of changes since 2.5 are in the release notes:

    (note some *relative* links are broken and the 2.6 directories are not
yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 2.5):

Note that this release adds new _default_ methods to interfaces which are
binary compatible.

RAT Report:


Please review the release candidate and vote.
This vote will close no sooner that 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 86fdc7e2a11262cb)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone
--branch commons-configuration-2.6-RC1 commons-configuration-2.6-RC1
cd commons-configuration-2.6-RC1

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you
then must check.

mvn apache-rat:check

3) Check binary compatibility

Older components still use Apache Clirr:

This step is not required if the site includes a Clirr report page which
you then must check.

mvn clirr:check

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which
you then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

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

5) Build the site for a single module project

Note: Some plugins require the components to be installed instead of

mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

6) Build the site for a multi-module project

mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

-the end-

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message