We have fixed one bug since Apache Commons Logging 1.3.3 was released,
so I would like to release Apache Commons Logging 1.3.4.
Apache Commons Logging 1.3.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-RC1
(svn revision 70938)
The Git tag commons-logging-1.3.4-RC1 commit for this RC is
8ccbd030e41114cf3d2059693fb9745c3bd271dc which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=8ccbd030e41114cf3d2059693fb9745c3bd271dc
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.4-RC1 commons-logging-1.3.4-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1771/commons-logging/commons-logging/1.3.4/
These are the artifacts and their hashes:
#Release SHA-512s
#Fri Aug 16 12:51:06 UTC 2024
commons-logging-1.3.4-adapters.jar=ae1298ef31b8be5f8adb143663963990fb69844c5c9aefa4b35ce150b107c2c6fb3044fa0d0569e1005bce1360d67484544d012fca7e8f3d363018fabd949c12
commons-logging-1.3.4-api.jar=061672ba3fcc1ae7f4fda7edeccc7af9dfdbb3ebe0b0a2d2a85c6fe84cb9b65bc48ba488ca7187f668726112d1bd5f1f630ebdc2313c761a0896e1a1c5fd1c2a
commons-logging-1.3.4-bin.tar.gz=b0223861f7e07b7c02b5f91976eac61d3a662fc1c97934acf2c04c8b184b5e52868d36ac4e4b418848021ca14f7e718188281400a4c437cfd96dee1f50570904
commons-logging-1.3.4-bin.zip=8094d828f82966c22372071fd92fa6342ccd496babdb4fa6bbaaab045a0c0fac78511bd73bd74be018b299a238bfb2f2c8cacf30a1ec43649c3e9044b2709f38
commons-logging-1.3.4-bom.json=8b92916911687060554b7cfa97f78d48d1e3f917eae51ad79288121b897d36e597c4d603247329050e6384eba9e3c410a954d010cdef17cf1b56e6732e8d20a8
commons-logging-1.3.4-bom.xml=4bdb0cff097ac281dfaa6112cbce21f47732b6aa0afbb7960ca2d3e0ba9d65af53c544ea5d4484abdf523a61177856b31232b21834eff5d8e82f9d60dfa2ed33
commons-logging-1.3.4-javadoc.jar=305db0734348c57e1292c08bd3a367d3520744858185c9a88f049d716f41c4fea81bf51a4fec8cf15d247ebadf779303a29763957d082c8f60f388c9b6d1a2ac
commons-logging-1.3.4-sources.jar=603758fd0cce2a24ef306b85de9f0601e85dfa6ec78bfdae4e089d8483635d761d45ed3dd369e98c6cdf22a67a06683406c7276caba58410f1663a0796aa662c
commons-logging-1.3.4-src.tar.gz=a4049d8d7ea0d97f337e169fa5f572e32be1882e07102ab004d8b2de74170cb075a251ee9603590d6e10bee5933651e8e33e108a734fc100e8b2d5acd669cb44
commons-logging-1.3.4-src.zip=1e7478be12b021f9ed230240e2c843b519f1f63b25513ca6584fc38ffa95a2e222820b51bdcc2ab5a295324cc44f163d7f0f2e1a2ccc20ae06b8a0af598ee03c
commons-logging-1.3.4-test-sources.jar=4d4d9788dc285c4c61d7d93bbfa432ed662cb7344ede10ea475db7ea0b1685f72e6821eb2c038c0a573f71cbf5d51ce39fedc695e4882e23dbf4d1bd24a1bbdd
commons-logging-1.3.4-tests.jar=ed3744b952d42aa0baeebd07a3b8bc6249cc13b8c16400302ac1a5ca2359cf1c47bbf629f23b0857f8331e13cf06cfdff01592880a854d590d809c2bd3e64a97
commons-logging_commons-logging-1.3.4.spdx.json=994827a18406e3fcee936092dc6f343e28858b3c7d1567ba9afc056f181ff063c47f2122691021aa79f324b90366aa1aa5ca3943c0be308d40de4ff5711634d9
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.12" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
Maven home: /usr/local/Cellar/maven/3.9.8/libexec
Java version: 17.0.12, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
Darwin **** 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00
PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
Details of changes since 1.3.3 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-RC1/site/index.html
(note some *relative* links are broken and the 1.3.4 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.3.3):
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-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-logging.git
--branch commons-logging-1.3.4-RC1 commons-logging-1.3.4-RC1
cd commons-logging-1.3.4-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.4-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: [email protected]
For additional commands, e-mail: [email protected]
