We have fixed a few bugs and added some enhancements since Apache
Commons Logging 1.2 was released, so I would like to release Apache
Commons Logging 1.3.0.
Apache Commons Logging 1.3.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1
(svn revision 65553)
The Git tag commons-logging-1.3.0-RC1 commit for this RC is
e0255a5845814802586b91c889ab3e9fc4bf9d68 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=e0255a5845814802586b91c889ab3e9fc4bf9d68
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.0-RC1 commons-logging-1.3.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1676/commons-logging/commons-logging/1.3.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Nov 26 16:38:45 EST 2023
commons-logging-1.3.0-adapters.jar=0b67e5fbca807b3d00ab5569cfac9fd14e268302ef514dee52eb1272762b35211d602045aefa71731108b900f6e0b7c78c3df39a989f3b86736e95a471b342c6
commons-logging-1.3.0-api.jar=d801af15997767abfbf0168651b19a55b8958e3b8c0106e054bdfd0098fdcb198c8dad0c123bd91448d0cb7b81851d4606319e43fed102c976b47143e481f371
commons-logging-1.3.0-bin.tar.gz=1fb9e4537fc59b75baf83b72a8e484604e6124ff7969b6f82955b29beeb5b86d9d115a494a6687e9a89a0b274f1ae9c226f289a7531334cc0451a3d4d5c2e3dc
commons-logging-1.3.0-bin.zip=43291b189957da5882eaf753792a041cd25f599b7fb6d960a16799ae450ae3cde59197fe4a664d59243a44c0cdd067eb9979ef2a225b762b0f56264a871c325c
commons-logging-1.3.0-bom.json=07580d9d52d4f93bf2a79e41388549a4f6f814cfcc5d6e05832036e480d0364e0bce212b79cc4e921d55587a00e0d1d1a1bcf8b3195fe9765e94f38294b60170
commons-logging-1.3.0-bom.xml=48a60112f79f6809a515a525837094b16e0ebff7daeeb561f20b639f18d47b3585f8e21595c469229caca9a0f2287649dbd8ce70105baa7d36bd621b68f42af7
commons-logging-1.3.0-javadoc.jar=73abbcf238b831d33fdb5c62406b6066183e3dce603535203b6fb0abc34c6aad9605eec2a5ca11981a2544b81447f8580f27a26f66e564f308c35152391c2cd7
commons-logging-1.3.0-sources.jar=ca39a42b2380c2c85800368546d8903b72e13f62bec665dd52db16f21dc214ecf81ff8a51f4739b5393b1d31326668e4ad5d0402eb4570728ad2a4321aeb6aa1
commons-logging-1.3.0-src.tar.gz=20cc40c7d7848da618801a86333f3984151d3089f806e5d7a1e92c83c1f90d330f1c7ded5d0ae70e48dd9de684f2e5da32de24fa2c406f6b419f77704c0e74f8
commons-logging-1.3.0-src.zip=516db2b8854846cf4c2bf5f4f3f4b7fc132183a7003eed0cff291f53f7f0a35d0dc4cc7eb362cd99ad5bf619620f16f7079e3015a7e01bda9e8802eca04a3fa3
commons-logging-1.3.0-test-sources.jar=159ec27c4343f926fe1cdc8977138b5200ef6f1284a3dddd361ae3cd19520d3e7b117e418272a4534b768859f1229e8ff7cd3555bed4f292c27e583a92fe9f2f
commons-logging-1.3.0-tests.jar=fb1d052e16ec83f9c6002a44ef79b84c08ad04b9ac3d378060e6adcf6d98860f4411c114837cca872427b1e5c663060a77f7157aabadf81fac1979ea34b44055
commons-logging_commons-logging-1.3.0.spdx.json=a416b9ae6d632f0638eb1c90184ecbe85bb91ce641b5ccea6ed64a144a6af80b20decaeb5d369aabb5e1cedd266d966fec5bc7517465414ab68036c526f9cb21
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.0.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
Darwin **** 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:27
PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
Details of changes since 1.2 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/index.html
(note some *relative* links are broken and the 1.3.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.2):
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/japicmp.html
Note that this report contains false-positives regarding generics:
Generics are erased at compile-time, so can't be binary incompatible.
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.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-logging.git
--branch commons-logging-1.3.0-RC1 commons-logging-1.3.0-RC1
cd commons-logging-1.3.0-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.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
