We have fixed a few bugs and added some enhancements since Apache Commons Release Plugin 1.7 was released, so I would like to release Apache Commons Release Plugin 1.8.0.
Apache Commons Release Plugin 1.8.0 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1 (svn revision 53018) The Git tag commons-release-plugin-1.8.0-RC1 commit for this RC is 414f394201ce23262895bb8b83bfa457a5884ab4 which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=414f394201ce23262895bb8b83bfa457a5884ab4 You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git --branch commons-release-plugin-1.8.0-RC1 commons-release-plugin-1.8.0-RC1 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1582/org/apache/commons/commons-release-plugin/1.8.0/ These are the artifacts and their hashes: #Release SHA-512s #Sun Mar 13 16:02:54 EDT 2022 commons-release-plugin-1.8.0-bin.tar.gz=34b50dff28dcb17ce209654a1fe310e02cfa860ce86b68e3fecc948da7bcdff395acbe6bd150588485b2e1a3418d154acbe02720c519e6a934ff69a1d65f063b commons-release-plugin-1.8.0-bin.zip=a8d40013a3ff62d8c82236c9236aadd632099708535d6f2f911d01a67f7c18bcdaa4b4c5171635344e20d78b7180e52f577eb0ddcde93b449e959b4ed6ad3e00 commons-release-plugin-1.8.0-javadoc.jar=108fd9bd1979f606a6ce25bfee6a4f9d7b87afcf28ab46ef12a99e6cbf0a062eb75c9d46a259890993d750009c3b0ac95b715ba97784b712eee4da27bcaed2aa commons-release-plugin-1.8.0-sources.jar=0b5eeb6c28498a61e7c23a66d72eb31e2a0a6fc1842ddef77513e266c77175639e106f9507e1b6067c0b0260fe0933b8e39d920941b3b83c80a53464bf405f49 commons-release-plugin-1.8.0-src.tar.gz=75c9e64b156586cfadc888ac045a8d185e1b40885aaf9c5912d0ff78fc0bcca4cc4ac3898ed58ad82ac94dc65d8ea9eef0c4b44f2762ef8d5f772228a70467b0 commons-release-plugin-1.8.0-src.zip=f39b8648b6baf62177f9a037f870133c072ea8093e6b5018f56555254525a5d16147002bf34c378e5a6b142b3c96c9ed2d7505cebd83515e726bd79912ab184a commons-release-plugin-1.8.0-test-sources.jar=a84cf4f0c8b49f058b8a8a2f1139f2e261ba8ecb3c107355c2abcf1825a0981a5e128345b91cc397e767aac815a9d8f9e88ac5fa70304c7324a35c9e7ebd0bfe commons-release-plugin-1.8.0-tests.jar=3d16b44b310c698002b460093bac5c44e5209615cfd3771d6c7c528c718a7918d25695a64cf8b71fb1a29a9c22efde2b1c6f101072e26ef428418722b2806d6f I have tested this with 'mvn clean install -DskipTests && mvn -V -Duser.name=$my_apache_id -Dcommons.release-plugin.version=1.8.0 -Prelease -Pjacoco -Pjapicmp -Ptest-deploy clean package site deploy' Using: Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: /usr/local/Cellar/maven/3.8.4/libexec Java version: 1.8.0_322, vendor: Homebrew, runtime: /usr/local/Cellar/openjdk@8/1.8.0+322/libexec/openjdk.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "12.2.1", arch: "x86_64", family: "mac" Darwin --- 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 x86_64 Details of changes since 1.7 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/index.html (note some *relative* links are broken and the 1.8.0 directories are not yet created - these will be OK once the site is deployed.) JApiCmp Report (compared to 1.7): https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/japicmp.html RAT Report: https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.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 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. 1) Clone and checkout the RC tag git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git --branch commons-release-plugin-1.8.0-RC1 commons-release-plugin-1.8.0-RC1 cd commons-release-plugin-1.8.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 -the end-
