We have fixed a few bugs and added some enhancements since Apache
Commons Build Plugin Maven Mojo 1.12 was released, so I would like to
release Apache Commons Build Plugin Maven Mojo 1.13.
Apache Commons Build Plugin Maven Mojo 1.13 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1
(svn revision 62637)
The Git tag commons-build-plugin-1.13-RC1 commit for this RC is
6c99abd8ae378dcfa4154b0ff1787de6b4bff968 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-build-plugin.git;a=commit;h=6c99abd8ae378dcfa4154b0ff1787de6b4bff968
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git
--branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1641/org/apache/commons/commons-build-plugin/1.13/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Jun 25 11:20:14 EDT 2023
commons-build-plugin-1.13-javadoc.jar=6e9f9b5fed3816149388a325f1adb2fb1596531deb94ab63c306eac3efcda6069328b3718399c7a616e82781bfb01cf24ea33d52a24d6d6497fbe2b5bc07b0ee
commons-build-plugin-1.13-test-sources.jar=02ebcf44d442fae28042cc5609319813d03cc4cf22dba195c40fd95cb5cc6ea3e5dec077cc809160378a6fe4da8d6ce9bab156f90b1cdcab9d3b3a739d96934e
commons-build-plugin-1.13-src.tar.gz=b8d91116c8e5994d3b13f59a2b18971132e63b6ced0ff53004f21d45c601c7abd2e7912574f1fd545821f9c2c82ff27eb41417a38795db2448a1621316db44d0
commons-build-plugin-1.13-bom.xml=91012ce5998e626e71605641020b6a21fdb03c859b423bec40b22d417faf362c315c1c50226fe9be5189cfeca86a9ce618d08b61a8be24b01f08683fd61d9c76
org.apache.commons_commons-build-plugin-1.13.spdx.json=e967bb2644b460058c5b6d2d9ffa429b6c1f1c3e67cb6d3c06c86ef03054a6401b1d364e737630bf69c2a50174cc40ca4f11d6fb13b5ac7f2a06cd0471ce52b5
commons-build-plugin-1.13-tests.jar=f6e9d604557354d0da8efe7c1a43f01c636154f280757d009dc7546b75d14653f53379aac8f62225c92f53a4841c0f536be3031b8663efbeb397a9f979ce9411
commons-build-plugin-1.13-bom.json=90f202a9dc7f6214882f8ae71ac4668b9bacf5e67362bb310b693cefb1fc56b3088e109575ad2decf6bff00f736ec42c7ee10882f48394f824ddbd08709b72df
commons-build-plugin-1.13-src.zip=e6ef7fe0f581f2d29e8c28dbd272ac52a7f28ea58bd6cfa879fb84650c889dddfb22d1e6f5014b77576b3a96052d37546d616a5f13b5b7517374b215e686e435
commons-build-plugin-1.13-sources.jar=b94b27a41492ffdfdaf96f182411efcc5ce6ed1582ad76d65b8db7d5fda87421caa148b43ee9f64d464bd05c4b0a18c105453308e500e8d1ce7c373e83bc3790
I have tested this with:
mvn -V -Duser.name=$my_apache_id -Prelease -Ptest-deploy -P jacoco -P
japicmp clean package site deploy
using:
Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
Maven home: /usr/local/Cellar/maven/3.9.2/libexec
Java version: 11.0.19, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
Darwin **** 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:22
PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
Details of changes since 1.12 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/index.html
(note some *relative* links are broken and the 1.13 directories
are not yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-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-build-plugin.git
--branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
cd commons-build-plugin-1.13-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 (not applicable for this non-Java component)
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
