We have fixed quite a few bugs and added some significant enhancements
since Apache Commons CLI 1.5.0 was released, so I would like to
release Apache Commons CLI 1.6.0.
Apache Commons CLI 1.6.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1 (svn
revision 64679)
The Git tag commons-cli-1.6.0-RC1 commit for this RC is
0d29a55998aa52be8832497527e266630f97c371 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=0d29a55998aa52be8832497527e266630f97c371
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-cli.git
--branch commons-cli-1.6.0-RC1 commons-cli-1.6.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1667/commons-cli/commons-cli/1.6.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Mon Oct 23 12:59:22 EDT 2023
commons-cli-1.6.0-bin.tar.gz=26487b81809d7bb79c21423d5a1556bcd0945db59a5096793fa14699b8b5001018707c72a3475a48a5071777f2c3c6a5d91936e1b7dcbd675ece855f1b929a82
commons-cli-1.6.0-bin.zip=9e7b89b2b32363acf9c4a773559697eb832c1fe1236859cbbd5e254bed5d205e95f46ef1cce563ca4612d672fc22a7239adcc3ba573b0fa23d80b967efe9b8bf
commons-cli-1.6.0-bom.json=532c4312167b76e2003f706e2bb7c45eec0782fe6d9977a0a5533f56961808c7e8d0c8b705acb11f5537fe5aabe0b6143c02184c666919d77a1fa7b4fed196ee
commons-cli-1.6.0-bom.xml=eb4ca6cc32dcb9f122fe86fffaea411cb768826566961582e618d1480341490a72503f225b7150ef21631f50ef3edfbbb5fed25d2b2b7d113e0b3e86ef8786e7
commons-cli-1.6.0-javadoc.jar=830e0c0ffb4b5d369dbd72af278897cbd2c3396ddb64d8b3ba53360073be5af4f96af988e8fe56f8bf85f661e15b709fdc7034522adefb2e8200e836d1fc193a
commons-cli-1.6.0-sources.jar=8ed0a9ce0e0064c3da1027b4615c918ad81d440fcea87e41e6461d178bed43bbdd2908876d004ffdb393df6fd0d4bfc12a5a8b3e0fdf48b47d9c96571d11895b
commons-cli-1.6.0-src.tar.gz=029088e7c51b657a0be5478685e1f689d6d39357957b3b8813ef6b315b4676ba4bd17b739dc15e09a30f8abfbe22e169c1c629f662477821adf0aa66474e1812
commons-cli-1.6.0-src.zip=c98b917e89bc4023e777736f2bb8585f4c62b01a82f2937167a34c12d40b65a0870269a38109e896e4eefef58cdc3f3e821def8ef524a0c267051c67da84975d
commons-cli-1.6.0-test-sources.jar=09b72e7050592e8d34caf7d08679011421f4bc90a9d8fc9f83d0e7629e4e7fb730f765cba8bae9bf048e9f3be806f9fa3a74423ff8982caa08048d71861dd410
commons-cli-1.6.0-tests.jar=89b2211fdfa912db46814ed0df7c39a88a6a2a233009684dfb0344ea16b5a28b5fcf13342fbe2ea3a802050f4b591e05f25f7b96bbbfebb16d2ab038cf2f713a
commons-cli_commons-cli-1.6.0.spdx.json=9abdae007fa94496c92deb2bcc203f0814692f1de741f5961c5fe3015d6274ea51a508f26ea79913d8fed4746c0eda1a6dfc1405e8056544847177b5ffa74c4f
I have tested this with:
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
Using:
Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: /usr/local/Cellar/maven/3.9.5/libexec
Java version: 21, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
Details of changes since 1.5.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/index.html
(note some *relative* links are broken and the 1.6.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.5.0):
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.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)
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.
1a) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch
commons-cli-1.6.0-RC1 commons-cli-1.6.0-RC1
cd commons-cli-1.6.0-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/source
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 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
