We have fixed a few bugs (one important one) since the release of
Apache Commons Logging 1.3.5, so I would like to release Apache
Commons Logging 1.3.6.
Apache Commons Logging 1.3.6 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1
(svn revision 82855)
The Git tag commons-logging-1.3.6-RC1 commit for this RC is
141c9ea8661fbf53ca710d12c462fab42986f0bf, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=141c9ea8661fbf53ca710d12c462fab42986f0bf
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.6-RC1 commons-logging-1.3.6-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1923/commons-logging/commons-logging/1.3.6/
These are the artifacts and their hashes:
#Release SHA-512s
#Wed Mar 04 23:08:17 UTC 2026
commons-logging-1.3.6-adapters.jar=f61f9974ec9526be4d794b34e8f9af66b26fcea6f5d045a1331fb0cf23179d478537963669f2894d32e4806463b14105684dcfe68ab22576347f0253054afd23
commons-logging-1.3.6-api.jar=1249732108803bb3f63f1fef86cd1bf906a020ae1bbca1c0737d92aade0e050bc6180ad4874ca852b6c3191197bc1f0d1c48fbde129e2c6d65c01a043cf8c556
commons-logging-1.3.6-bin.tar.gz=15ed28cf924b189c6732e723a0e66f8590caee204800746c639b104e7bff066738778f1c2645a0b14d015e0f2ac7d992d538106c55a216934eebd8489a580d48
commons-logging-1.3.6-bin.zip=d56185df5b1374fcebf94c7f81915a3a9c121265683f149d939139849256087129e3bbfdfbf3381e06761733d6594becb815e71472b3a6b9b9526944736bebd6
commons-logging-1.3.6-bom.json=a889c6471a7c5a2f968d894c2c101836959e2074e9e5e5173c4efae9f273734b108b8cbc53bbfa7002e23bf4de7b08e787749cae3e81bae714840dcb7a9aa8f1
commons-logging-1.3.6-bom.xml=dca89d83cc017cfdb536bb3c0376ac6e1618e03a1c813c542a13e0e394a6347b1dd6957695ad1552a2b6964f3a6bc1478f84caf16ead0e369ac72040a530be42
commons-logging-1.3.6-javadoc.jar=b12e52f4d22792fe9f502d8178e57bf00672c34fb04e398456ed0b692e4e86108d62ead55cc345c8eef0817470297d9cc90adce25860ed3be06158e4432edf34
commons-logging-1.3.6-sources.jar=d817792ebf865570f132023d9eb2ad4f61d95854dc0b0c80281dfa38af9b25397ed8e274ffa6849e55b0905ff6417f5aacbebf1391fd993eda5d37d3e9d2387c
commons-logging-1.3.6-src.tar.gz=66b7be2f24c3e2900372645eb803613425aa8d1b11337cd57a87e52eef63b25a193ac0bcde361fd7cb5521582dc26030288f97f9410777570b8f460ae5cf6393
commons-logging-1.3.6-src.zip=2b920ca8b12f8aa524d49fe34cd9726c7f9efc1989a5ead1675abb6079fcee8e0ace6662cd3001e544337c51f8896f1a5b80bc54fee6ddee24ce8ff9457e4a6a
commons-logging-1.3.6-test-sources.jar=7700fed34ab414f84dad9447c06200c4f93f86c37dd8280b3bcb30ca0110a0d455543ebaabd2b1875fd3cb4c34669a5f48d0ad1d84d78f96377320f6d4058604
commons-logging-1.3.6-tests.jar=15322698cb5e361c1db0817355d54bbdc6da5240dbc0407ca52f0bcff8b46eccac5cf9609152b39653be92cd59d42c0d34b638faeb57356e6efca839c4756ef1
commons-logging_commons-logging-1.3.6.spdx.json=f32864863350707b7f42022dca4cb57f28e5fa91062b6c9dd53210ea50284cb224d51cdca73a4db675007958bf678b408a3be7ad4ffae9405ffb152c217091b6
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "21.0.10" 2026-01-20
OpenJDK Runtime Environment Homebrew (build 21.0.10)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.10, mixed mode, sharing)
Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /opt/homebrew/Cellar/maven/3.9.12/libexec
Java version: 21.0.10, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.10/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "26.3", arch: "aarch64", family: "mac"
Darwin Garys-MacBook-Pro.local 25.3.0 Darwin Kernel Version 25.3.0:
Wed Jan 28 20:48:41 PST 2026;
root:xnu-12377.81.4~5/RELEASE_ARM64_T6041 arm64
Docker version 29.2.0, build 0b9d198
Details of changes since 1.3.5 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1/site/index.html
(Note some *relative* links are broken and the 1.3.6 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.3.5):
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-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 530AA5F25C25011F)
The following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Download and decompress the source archive from:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.6-RC1/source
1b) Check out the RC tag from git (optional)
This is optional, as a reviewer must at least check source distributions.
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.6-RC1 commons-logging-1.3.6-RC1
cd commons-logging-1.3.6-RC1
2) Checking the build
All components should include a default Maven goal, such that you can
run 'mvn' from the command line by itself.
2) Check Apache licenses
This step is not required if the site includes a RAT report page,
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn apache-rat:check
3) Check binary compatibility
This step is not required if the site includes a JApiCmp report page,
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn verify -DskipTests -P japicmp japicmp:cmp
4) Build the package
This check should be included in the default Maven build, but you can
check it with:
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
4b) Check reproducibility
To check that a build is reproducible, run:
mvn clean verify artifact:compare -DskipTests
-Dreference.repo=https://repository.apache.org/content/repositories/staging/
'-Dbuildinfo.ignore=*/*.spdx.json'
Note that this excludes SPDX files from the check.
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: [email protected]
For additional commands, e-mail: [email protected]
