We have fixed quite a few bugs and added some significant enhancements since
Apache Commons CLI 1.4 was released, so I would like to release Apache Commons
CLI 1.5.0.
Apache Commons CLI 1.5.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1 (svn revision
50583)
The Git tag commons-cli-1.5.0-RC1 commit for this RC is
e81a871025cd2dd5bc1d3b473c3c495533e7b8f4 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=e81a871025cd2dd5bc1d3b473c3c495533e7b8f4
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch
commons-cli-1.5.0-RC1 commons-cli-1.5.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1573/org/apache/commons/commons-cli/1.5.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Oct 23 17:47:54 EDT 2021
commons-cli-1.5.0-bin.tar.gz=7d952d49f1899f5f7ceca28f806730013b93004d852dcf3f3ce0149e932fdc387bc289c22f6f9e52835611813571925f0c8563cc11e2aebf5a1597c8be7d2222
commons-cli-1.5.0-bin.tar.gz.asc=d77f4776d6380a6618d5c850fe944ffa2d4b1277f5d6bcfeb38088a42d52492c189bfd3d8670e2bd5bdd171039b460a3575018de2afc633609fe55b51d75e66d
commons-cli-1.5.0-bin.zip=216d8b1f4c3e6b6337a820ce0296a29982664c230139ec5d8a2c1c554c205e2cc8584c3e7bee43eebe042b3731454f6c5caa9bff87a54c9e3955a955f99d5ee1
commons-cli-1.5.0-bin.zip.asc=00556819fd85478d939c7bd4cb72b13f2f4f1578dcbfb64e7c4a64d42bd06c4ed7b0c4e4892d42a2816fb38e6a4609a72cc2dcbbb3d36b5b91bd6963e3bd9a6d
commons-cli-1.5.0-javadoc.jar=332eec1017e8f7dfee218426414df9e45428f2458629728aace8a2fac3afaf0aab64467eda1f1d6d075a7c8abf06bf39f0cb3f1e6b1c9e45f53deb0ed595063b
commons-cli-1.5.0-javadoc.jar.asc=ceba76dc81d26f14a36ba4e8f00ea3a50e2cf828ba91b5303f369dc0b876bc1e1141a3279df6345209f042f4cdd68b80f7447448f63e004b1ddedf30cbe45782
commons-cli-1.5.0-sources.jar=21045e9ec71c420a9eba3539ed96bf349e9053f6cc7f0d1a67ed40a699b37993bbb0c7b8b9a97ea88625f2235da23275533ab7ac8cde9111f72f7314369dc132
commons-cli-1.5.0-sources.jar.asc=a5ff72e46e99affb7ea6caecb525ed4f1a3079e7b9e061bf5902f96e1bf4ef7ac4de54c16605e3dd4686b81bdd212ea83f0d632a126063c82dde300af2676c72
commons-cli-1.5.0-src.tar.gz=aa2165695177c3e4561f68585cafb5434758138d8a863f3db1860477f660cf78664d2afb07cc3bc767bc8fa87befc7eaa5bdead423ee8b883c62ff00aec7cdda
commons-cli-1.5.0-src.tar.gz.asc=619b1d3105fffa9841a0f551da482374c276245ff6aec58bb6d4d175146fe3d841c722cd5a8c13e9a686628cd0729c133ece266574b04a042cf7bfa4675b5bda
commons-cli-1.5.0-src.zip=de9dcb3d9a1cb65279b1d9604ce61e3522d661e024dd8062c811b07a52761c0a0e2290a01ef91276c8a2155cdb94e05d1f6c76557c29fc2c743b9196731b914b
commons-cli-1.5.0-src.zip.asc=f4ee644ac50636182a39cf2ee700e91eb46f340ae2772d51c4764a4e85da3fe02703b8391fb11f386cf6ed25ab24a5e2b91ca7e62506659574b4ae5010a52039
commons-cli-1.5.0-test-sources.jar=23ade4f439e5de53e1b654b27a4857e91c261d25a62fcf833227055d4dbf7f7aad06a6e63b7fb043870a6911e3dfda74c4acd4b671860293f96cc3e41fde2d2f
commons-cli-1.5.0-test-sources.jar.asc=a1aaf3a4ca273a8ecf2b619faf63cc917568f9e6bbcb1fcedf816dd39f30567638dd272441e1feb8c02d7a9692265b43075bfd01ea7e449dfe8e38dfde31bb14
commons-cli-1.5.0-tests.jar=d6c01aa748dab3747ebb28f675ed0395bfe41d73c9ddf6fd1968f80b1b3edd769e0fa01ac800bd378319bfb03dd9df74dafe51f4a870338c4c9ff841589cf999
commons-cli-1.5.0-tests.jar.asc=04025ee90f190200b7e07433362d0da45cea23d21590aa1d75c0134159c3ce90ecc6df2f0ada47ca7a52af21e849a657c16d5402e90a4c24730cf874412d61ba
commons-cli-1.5.0.jar.asc=d1bcc1690ca026bc4f8709c6a7544818e6c4b6348beb13ee0c7f0d5f7255f3e403349e63a74ac18c3ba4885db1518f841a93dcdd42d9f755663fd9999717ad25
commons-cli-1.5.0.pom.asc=68a82edaae73a71740624dad1466e2101f5b1152c7bea2cd315fb6ed249a59998afdd270706f760453dd5f047caeb8f91c6304610a8687379d2b689450e477d3
(no need for .asc hashes!)
I have tested this with ***'mvn clean install site'*** using:
***
Use the output from "mvn -version" for each combination you tested.
***
Details of changes since 1.4 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/index.html
(note some *relative* links are broken and the 1.5.0 directories are not
yet created - these will be OK once the site is deployed.)
CLIRR Report (compared to 1.4):
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/clirr-report.html
JApiCmp Report (compared to 1.4):
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/japicmp.html
***
Note that Clirr reports several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.
Errors reported:
- methods added to interface: OK because that does not affect binary
compatibility.
- etc.
***
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
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,
Rob Tompkins,
Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314)
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 https://gitbox.apache.org/repos/asf/commons-cli.git --branch
commons-cli-1.5.0-RC1 commons-cli-1.5.0-RC1
cd commons-cli-1.5.0-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 packaged.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
