We've bumped dependencies since Apache Commons Release Plugin 1.8.2 was
released, so I would like to release Apache Commons Release Plugin 1.8.3.
Apache Commons Release Plugin 1.8.3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-RC1
(svn revision 72767)
The Git tag commons-release-plugin-1.8.3-RC1 commit for this RC is
a932a5187b5aff9d76ff13c91245e0bf6af464d8 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=a932a5187b5aff9d76ff13c91245e0bf6af464d8
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
--branch commons-release-plugin-1.8.3-RC1 commons-release-plugin-1.8.3-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1785/org/apache/commons/commons-release-plugin/1.8.3/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Nov 03 20:06:30 UTC 2024
commons-release-plugin-1.8.3-bin.tar.gz=1a8640280c4a3d17cf2e181ed92d75caa6e13b397e6f3e6f99a7c4a4de47a9c473e5edbbbbe2edd35ed07db7e1a8a1196a9cbd021b2d8000c2372c1d8072dd7b
commons-release-plugin-1.8.3-bin.zip=85d411d7ab26f4d40b76f73d2a07d26fdcf76979d6e3b2e11082dcb66a2788bed56ad033e0f32f1eb327e99d141d55fc4f34f3f96512cd46e5243bdf63e693e2
commons-release-plugin-1.8.3-bom.json=ffbdd86cda2d19a3d49d869c297c6b72bd28e592836a23faeb917561d17e5306a5a5c679bac1c945913d67d97f061b354820e0b75feaf90671dccf1c08869d60
commons-release-plugin-1.8.3-bom.xml=6319e85b3a28acbb13780cadf64184e59781bf64bbf0f5165db2477939bbbe269dba4993f22318f5056693416a3ae53c5978e1f52be8517a1cab0ee014e1ac3b
commons-release-plugin-1.8.3-javadoc.jar=ef7d6da42d45eeba0ed9ebb8cab23428ec8a47f5898cb5bb8fb1758270065972783d4bbb24f1bee1cef63e82315ad9ecbe22992a7f696f6ae0ab4cba117380a6
commons-release-plugin-1.8.3-sources.jar=cc361259bebc2f66c2e1476b79399fb087ece786e720ce995c4142f652d792ebb649b1b328ce03668a33246341a67fc72126e4fb04c3b0355c0b8ca5022efe2b
commons-release-plugin-1.8.3-src.tar.gz=e4872005cf4facd700d1cf39c4b61827f11a6e3cd55de8e8ed90d23a4dab40cc9c8c4bdcb6aa6b27d039692706c8a334f8c01ff72a03930503e24949c491975c
commons-release-plugin-1.8.3-src.zip=1bbacad8df5301845829bbfe12780804783ecd94e90e1a1a5ae12b176bbcc06e2450257c9005d05b47ca972e38a479d9dc4cb6f844b7f6d0f82d38a7a14cf56f
commons-release-plugin-1.8.3-test-sources.jar=a47ee65313633c687d688161c2ac551cbaea2cb893ad4c272441fa8e6a8e644f35df899c62d3d412ba03f6a4fdf2409f15533c26a52697253d1c8230394af176
commons-release-plugin-1.8.3-tests.jar=ccc5ec9187bdc96d6987990615dea53e69e3ed8e092e12ca82b5c8d1c8cabd6f5e90be498e212cc541e90fc9c8d30e801f27610b90b675bc001f8e0d9fa235fc
org.apache.commons_commons-release-plugin-1.8.3.spdx.json=2a746d44e1729b0daec0058f30a851193d04e8f23fa69f8fbf4046e5631471eb7b47d5300a86d6ec936072e5d096844fef99a1731c921523bd6f5506030d4b8b
I have tested this with 'MVN' AND 'mvn -e -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:
openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment Homebrew (build 17.0.13+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /usr/local/Cellar/maven/3.9.9/libexec
Java version: 17.0.13, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.13/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.0.1", arch: "x86_64", family: "mac"
Darwin **** 24.0.0 Darwin Kernel Version 24.0.0: Tue Sep 24 23:36:30 PDT
2024; root:xnu-11215.1.12~1/RELEASE_X86_64 x86_64
Details of changes since 1.8.2 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-RC1/site/index.html
(note some *relative* links are broken and the 1.8.3 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.8.2):
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-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, 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-release-plugin.git
--branch commons-release-plugin-1.8.3-RC1 commons-release-plugin-1.8.3-RC1
cd commons-release-plugin-1.8.3-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.3-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
Note that the project reports are created for each module.
Modules can be accessed using the 'Project Modules' link under
the 'Project Information' menu (see <path-to-site>/modules.html).
-the end-
