We have fixed 2 bugs and added 1 enhancement since the release of
Apache Commons CLI 1.10.0, so I would like to release Apache Commons
CLI 1.11.0.
Apache Commons CLI 1.11.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.0-RC1 (svn
revision 80578)
The Git tag commons-cli-1.11.0-RC1 commit for this RC is
d74613321325f6081fa0206c4ab608ab65d80e2e, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=d74613321325f6081fa0206c4ab608ab65d80e2e
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-cli.git
--branch commons-cli-1.11.0-RC1 commons-cli-1.11.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1874/commons-cli/commons-cli/1.11.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Nov 08 22:40:23 UTC 2025
commons-cli-1.11.0-bin.tar.gz=dce3ebfb3ba0af9c9d67df7b83ec7348a07d436c47b0be06a1646e19bf652cb4cbe6b6c0b303e4dd0883cf697ca32587108d057b454a9cc8fa6553251114b44f
commons-cli-1.11.0-bin.zip=6bd353d5223d064445a27d0c97182ef99acf179702c3ea69be6b7088d958f73a4ee4072323085e93d07208bc3c997f7f6893a2ffcc9cc9ed6ef178fa82050a04
commons-cli-1.11.0-bom.json=3bfdb257927cc48d3b5995554015a8bf1bd51080b92f227f04530af26d15e9f7a1a29f92d648ee97e5a40da277b6e83fb9500a997223d98278d32e161e75d49f
commons-cli-1.11.0-bom.xml=3f48894613db5485258985603368b3caaebaae5483de2d5856256611afec5591aff5c1914c080f39eb02d34d9f83d110b4a4e030edbbbfbeb9a85701c0f2ed0e
commons-cli-1.11.0-javadoc.jar=2bd670274b6234cc59128ccf4ba409913afb31c87f2c343d4267cca632b878bffa4fc295d1c693e8a610ba9435460c6f9a35f041ff2dfd5efcd5941012e623ac
commons-cli-1.11.0-sources.jar=b59ac0739a001f7bc6b8d7df187995cf2ba0a3fece702fe34933523989867c5060113a67da15b3ff1bf447d3a2ceedc593b598c8c65a786da5cce5cb26495f4b
commons-cli-1.11.0-src.tar.gz=161b4efb628943c3292fc89325632147a4677f7f68bfb06d7d868fc8df07f1ec11623f812d69c3434938487af96e810ff3431ae1d384108d6847cad849160d9d
commons-cli-1.11.0-src.zip=7918509f2fc6fc471d23839b9bf1dac1d8ab471327e1c6c956057fca748c4b3cfb96ff0d9bd8aa951d5be4d503eedf97cfe10db1a69031c0371b2285c05865a4
commons-cli-1.11.0-test-sources.jar=2aef94cf1fbe1f194d355260b90e770870b3be50a551290f798738de2283a1aa3496f9d21bc4c031d7eb51fae5bcf0565cd0e27ed8f244be2a76c4dd527252b9
commons-cli-1.11.0-tests.jar=5f22408edad61850d6c0a15e66fea8837226f959aaabf8526cfe98d5c3744e1e65199ee0f223886074b0f0699b417708443433d330bd437aae61e3c49d41bee4
commons-cli_commons-cli-1.11.0.spdx.json=d1b81bf71b0c240d085b794892baa0728a532cece93e32878ccf36b48d4d2c23356751d12d8769029f93fd785d1f2b94841d880b261c5aed8fc45a9792c8b5b0
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "25.0.1" 2025年10月21日
OpenJDK Runtime Environment Homebrew (build 25.0.1)
OpenJDK 64-Bit Server VM Homebrew (build 25.0.1, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 25.0.1, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk/25.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac"
Darwin ****.local 24.6.0 Darwin Kernel Version 24.6.0: Wed Oct 15
21:12:15 PDT 2025; root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041
arm64
Docker version 28.4.0, build d8eb465
Details of changes since 1.10.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.0-RC1/site/index.html
(note some *relative* links are broken and the 1.11.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.10.0):
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/cli/1.11.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/cli/1.11.0-RC1/source
1b) Check out the RC tag from git (optional)
This is optional, as a reviewer must check source distributions as a minimum.
git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch
commons-cli-1.11.0-RC1 commons-cli-1.11.0-RC1
cd commons-cli-1.11.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]