We have fixed a few bugs and added enhancements since Apache Commons
Codec 1.18.0 was released, so I would like to release Apache Commons
Codec 1.19.0.

Apache Commons Codec 1.19.0 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/codec/1.19.0-RC1
(svn revision 78257)

The Git tag commons-codec-1.19.0-RC1 commit for this RC is
351cb22e1e1948aaabb39a463dce631bea156125 which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=351cb22e1e1948aaabb39a463dce631bea156125
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-codec.git
--branch commons-codec-1.19.0-RC1 commons-codec-1.19.0-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1848/commons-codec/commons-codec/1.19.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Jul 19 17:19:48 UTC 2025
commons-codec-1.19.0-bin.tar.gz=0bbf1b4ee0c820eb89cca8cd5b25b2506fdc7759d80ca03b57d90412a314cef7c72f5d2862ac7a3b997ea9eeb60587d7e67ad8fe7601b936dad412e7ab4cdf6a
commons-codec-1.19.0-bin.zip=7adcf2b49ab19a151119fb9e24e3762db5d15ab09a5def91593c8067c433bbf77c22d109db5ed03c64e262fb896e581cdb4a6104b1236594d05540f2e53af460
commons-codec-1.19.0-bom.json=1641f12c82f1373545b3d05b31906962bb2d0aefe20779911af5d184bc0b402d08a8d607164618c0c0a89a4ce6fde5df8b26059c83249e9c6becbb5b01405eb9
commons-codec-1.19.0-bom.xml=464fe05b49e2da833aea33c16d71455eeac4ec42538a30e65b35300eca2efaad482693ba04f23e5363188ffaa37294ed6b6fea3ec198c752b86fa1bacf9fbfa2
commons-codec-1.19.0-javadoc.jar=6f60afb0b5466ff9b6f80c1aca24c5adf67274e99976fe3cc1b13d2a2b7053d767cc79dca1ec970ba444df3d6c5610b00c920b2ae2342228aed47d87ac5a220b
commons-codec-1.19.0-sources.jar=827156c0566f7f8ea5043b0a963c65f0e6b9bf009a48e7a4cd77f158dd300203841eb7c407ec9cf147b2af53b8f7bc7bcf679c7bb54f4b46110ff70a50fd8202
commons-codec-1.19.0-src.tar.gz=65532419ea55f6d829ea46ff04806ab539a4e904950af9b780632c41011186ef1f38ebc739e3db115b2dd79266574316aa8c8e6e83c688accc8b1e8f4c2a3e83
commons-codec-1.19.0-src.zip=9c927244c88048e8f42c69694dde0f3434591b1899e7f4f65077c5816c2b20df9fe457f474636b0c77f51e2651992651e14abde9a746e07631b517fc33497fd8
commons-codec-1.19.0-test-sources.jar=99b3b0fa3286aca3d7110e2be46cc565ca18c2ba33c7fc72424446152e74e821bca9bbc62d4ac441964f2f7c5f1ca49f02d514b99e579208ac2b97c9272b2a50
commons-codec-1.19.0-tests.jar=56f209be7fdcccf38a662aedf8b847d4e7392137b8c2a6f34d4c924af5b8d8d62140632e7114c93361c18230f7d5e51d9f778d89c7c4ae9ef4e3b9048edd3e5d
commons-codec_commons-codec-1.19.0.spdx.json=9ed0b5e4462830e2dcb4908a74d6fc35e295b32003b68528815500b2cf27b92212ae2f5fd941a8ecdb5afcf1e85feca9c5418b2e72e2447604283a5c945cc58a


I have tested this with 'mvn' and 'mvn clean install site' using:

openjdk version "21.0.8" 2025-07-15
OpenJDK Runtime Environment Homebrew (build 21.0.8)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing)

Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 21.0.8, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac"

Darwin ****.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22
19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64

Docker version 28.3.0, build 38b7060


Details of changes since 1.18.0 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/codec/1.19.0-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/codec/1.19.0-RC1/site/changes.html

Site:
    
https://dist.apache.org/repos/dist/dev/commons/codec/1.19.0-RC1/site/index.html
    (note some *relative* links are broken and the 1.19.0 directories
are not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 1.18.0):
    
https://dist.apache.org/repos/dist/dev/commons/codec/1.19.0-RC1/site/japicmp.html

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/codec/1.19.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)

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/codec/1.19.0-RC1/source

1b) Check out the RC tag from git (optional)

This is optional, as a reviewer must check source distributions as a minimum.

git clone https://gitbox.apache.org/repos/asf/commons-codec.git
--branch commons-codec-1.19.0-RC1 commons-codec-1.19.0-RC1
cd commons-codec-1.19.0-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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to