Hi,
you may consider whether my proposed fix
https://github.com/apache/commons-cli/pull/382
for https://issues.apache.org/jira/browse/CLI-221 might be good enough
to be integrated before the release.
Bye,
Joerg
Am 30.07.25 um 5:18 PM schrieb Gary Gregory:
We have fixed a few bugs and added enhancements since Apache Commons CLI
1.9.0 was released, so I would like to release Apache Commons CLI 1.10.0.
Apache Commons CLI 1.10.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.0-RC1 (svn
revision 78469)
The Git tag commons-cli-1.10.0-RC1 commit for this RC is
04581158dbebe688518a6d384cf7b611a074ef7a which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=04581158dbebe688518a6d384cf7b611a074ef7a
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch
commons-cli-1.10.0-RC1 commons-cli-1.10.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1856/commons-cli/commons-cli/1.10.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Wed Jul 30 15:13:50 UTC 2025
commons-cli-1.10.0-bin.tar.gz=15a7fffced7a2bf386de744e0409ec974283793bdc6a3a943a1ef2df272b5bfa7e2b7e032a80f53d255f3f8de5b1e4f788a9abf88b17678d68cee4699ffbdfc8
commons-cli-1.10.0-bin.zip=63c6fc458933e8a86932468d77484db495029ca3ef6edd3e2c4bb578fa82bdf10a4b0766fb27659fc9f2175e537244fe82cfa1c6d0ca8dcd8ddc39051e1f8281
commons-cli-1.10.0-bom.json=ee0ae71723c56f8095e0a79c9ea62f791a27ec15139b4c223a5649b1a4d07ecd2e15f17db4272159ff552056f61a28abed8d3281ce276004af4b6c716e6167f9
commons-cli-1.10.0-bom.xml=569de812a8dd12a72aab07fbd414766f73ab386dc5338d44fb51ab958505f05b20ab5de7dfd022e61b1ca583c00ae493dc197398bef059ab4fdb2de3e4fc9e51
commons-cli-1.10.0-javadoc.jar=2c4eae1ecbae7b629b922df3ec428c5ee1931e23d7173807b5aa46fd49ec028eb045120106a989465a9b300981c370db5c8e36e16ed234458a5a074c620b9d98
commons-cli-1.10.0-sources.jar=5d27612094cb6d3acaca5dc48c3ce1e81394cdf7917d2577b69b8c0320b49738e3b7c84cc547debf9442a4bab11319767fde9f581f4775750e872deb030d11fd
commons-cli-1.10.0-src.tar.gz=245951919a88068f692fc4cab906cb210bbefd853d851167d5c34fd4aebab7370766458033c47cf8174d7a409c4364752770b573252d19746cbb9a0e2c8c255b
commons-cli-1.10.0-src.zip=f5ada1cc1cfaaa91b58f09f723a1712d109608c9f82fb3b3a905a78a5bc179ce1cd2d3b3e102ee5b5bc7fe432d76d4593166c2ba0bd676a2b81d9b494185bedb
commons-cli-1.10.0-test-sources.jar=6e1680aafdeca3b4907e0a838fd090561103d9ed73d2cc4a39dc27618e60b616d4daedf624c705ca66facb90bcfe1d746e947eac742ad6e245f904d260a4515f
commons-cli-1.10.0-tests.jar=1d82881deb4cd219d0e02359c57ea1e6f37cd6f15296eef0850fba0ae16976f6e75663227876406b50618ccc6cc0fce744a7f5423411f2832982bec7c646f1e0
commons-cli_commons-cli-1.10.0.spdx.json=6ff6567ffda04dd80046b234eb8ab1f3ec7902756430f72d9c0d0ae166f93689c0a91908bd5d450d857066c66db97af61d9c9c69ce88d67c5e714778000bbfd6
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "21.0.8" 2025-07-15
OpenJDK Runtime Environment Homebrew (build 21.0.8)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 21.0.8, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.6", arch: "aarch64", family: "mac"
Darwin ****.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:40
PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041 arm64
Docker version 28.3.0, build 38b7060
Details of changes since 1.9.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.0-RC1/site/index.html
(note some *relative* links are broken and the 1.10.0 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.9.0):
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/cli/1.10.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 86fdc7e2a11262cb)
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.10.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.10.0-RC1 commons-cli-1.10.0-RC1
cd commons-cli-1.10.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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
