We have fixed a few bugs and added enhancements since Apache Commons
Logging 1.3.1 was released, so I would like to release Apache Commons
Logging 1.3.2.
Apache Commons Logging 1.3.2 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2
(svn revision 69106)
The Git tag commons-logging-1.3.2-RC2 commit for this RC is
77474c5661ca60e18fc9499a4c4195df0c63ebe2 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=77474c5661ca60e18fc9499a4c4195df0c63ebe2
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.2-RC2 commons-logging-1.3.2-RC2
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1727/commons-logging/commons-logging/1.3.2/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat May 11 17:49:03 UTC 2024
commons-logging-1.3.2-adapters.jar=06715cd88b99c4a26e49cff7dc059104793a2d2a516cb7457486b41c63ccb7cda6faf8a4cef2edaa05779d7de4c95b2ba68214881893d87e4b5d6d2f49607021
commons-logging-1.3.2-api.jar=c621d38229834fb42a99d485af0ddec9d7f842d5177eaacbbe1e1ec13820621af436b717c51560bd5dce07fc5f3eef0f58da81d3c524cdd0c277ad986149be49
commons-logging-1.3.2-bin.tar.gz=e970524f480e43a4e65f9518db3a1f8fe79f63339049fb2d03f36ee4f653e6eb9ca395afdc2dbacac4334ca379787073c542ba57caa87f78d888d2eee48ce042
commons-logging-1.3.2-bin.zip=c2b99aa7e1bb174214d6ad851dc61a07f3098c035ae5b36792fbc3cc9d8ba01bbe477035397b9b7361c09344f28f3eb5666b7b52d897b73fbd4e4415d80b72b3
commons-logging-1.3.2-bom.json=140a60c1bc7960ffd0e4eb733efc8733778a0228adeaff2dd4d9ee6ffd7bc4f5eb7f6152b18f3d5c662e4041c56cfcd1d4f103c628a9177d5cb475db463c1aea
commons-logging-1.3.2-bom.xml=0f2e5b2b45ed7d22ea5d03b6641b1518e98cf1ff4b641b475ececfe91ca5ea65877d18a4c647116944e71a55ce68a20dc93c3b1b98faa50d2d5b0d1c22a4ac56
commons-logging-1.3.2-javadoc.jar=575e4b4f94455f26df7d1173d237a3837c32bf5a957b2f024dc7bd6c903029cf0c4fb544a0c2b2b867ad9d7a0b947799ba035fde3f51c4b81cabc920b9b111bf
commons-logging-1.3.2-sources.jar=87a8ce1dd2238d2962fc727bd4d09d81e352a028fe144c8113d0c983515c17765a59a582c19339f522d950de281fbf683b807e7d2c0a13dfb8a8ed2609f2cd18
commons-logging-1.3.2-src.tar.gz=d31c8c44ba851018baae4381320ebe8c585c7fd870ef7e0687c2655722dbeac415f96648d6bee21d4849e1890747b2b78b6995b3095ddd763840a4698890940e
commons-logging-1.3.2-src.zip=07dc4d5311bbaaa3fd3952c3f77bd887c344415af8fffae1a7b5c41d3d96c9c8a8d18f3b3f7956851e07b89628dfaaa4d087af42f394318678a204f43fe86731
commons-logging-1.3.2-test-sources.jar=b9e816cbea3197ad706a9866629fcf0b2d33410ef6f9a15dbe92aea8baa28adb7dc247376ddefa6128384275696160b5ae504d97b73a7dada754747e56d89eb4
commons-logging-1.3.2-tests.jar=fd106e33f28d13896e4f8f93d7969777ec3d99d318b0fb10e165f81bae598d1473ecc81dadaefe7114025a73283063f86cd3465385eb03ba6e964e6c294c9ddb
commons-logging_commons-logging-1.3.2.spdx.json=f703382e3b70b9f63e50aa8c788cfbe6deb8fcbc62526628e52162b2afe060a67813e0491bd98d238242ac9dff09d648df8ef3decf48ee882ecc00e85d7ee81b
I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:
openjdk version "21.0.3" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 21.0.3)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.3, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 21.0.3, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.3/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
Details of changes since 1.3.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/site/index.html
(note some *relative* links are broken and the 1.3.2 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.3.1):
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/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.2-RC2 commons-logging-1.3.2-RC2
cd commons-logging-1.3.2-RC2
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/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
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
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-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
