[VOTE] Release Apache Commons IO 2.22.0 based on RC1

We have fixed a few bugs and added enhancements since the release of
Apache Commons IO 2.21.0, so I would like to release Apache Commons IO
2.22.0.

Apache Commons IO 2.22.0 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/io/2.22.0-RC1 (svn
revision 82001)

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

Maven artifacts are here:
    https://repository.apache.org/content/repositories/orgapachecommons-1911/commons-io/commons-io/2.22.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Mon Jan 19 16:26:56 UTC 2026
commons-io-2.22.0-bin.tar.gz=1fe76d86b91ed7d68cd8b1113a64cafd1634d18e88c7668ee3aa7d85393dca65f062ed4396a5527a392590c7ccd31222a52c4c16c84705780ab023bb807760d2
commons-io-2.22.0-bin.zip=d29f86ec3af9d835b0661a07f60ec54d890498e149f8be7b957233f758b80ce805521f7aa299a3aa08c799d533e2e01852109f856fad857c51e060b2521bd574
commons-io-2.22.0-bom.json=4c60288b55646b10477366adf7cf377851138c74b03aee6a9271759ef98612067a6a9b599e04875ff598e69099f0c1ed59f3e9d27942e6dda71f933830038156
commons-io-2.22.0-bom.xml=15d218ec2ce3f5a7f8617b018b7b8ba72326d42da6b43802bdc6c204ed14ce33ae86643cf12e42fb2e5f36c9723b739f27f0e3634ccb1cbd8055045384763e5b
commons-io-2.22.0-javadoc.jar=1315329da2aeb1d2c75b5b23805b8c9d18b655d9c06e3f63670393e04a00fb0649956f297a976d8b9aac58d349932d19a7b110cc51182e52e8718a6dcd55c7a9
commons-io-2.22.0-sources.jar=774fac027af44b1629a6e483b4a03557a974f170c55359e8a021a76feb5f67f1fb38ff07d01588249d44683da440b912633320f12e50cb15d1e0e23f2a5c95f7
commons-io-2.22.0-src.tar.gz=3a468d6766ba4e6d0dd011f7ffd34346341f5f7fda2fc4d9f018ffeeae8a3d47132bcd15b85f7331b14ba95b68bdb9e2a4a3f942e1a4c208e8727f78444cc125
commons-io-2.22.0-src.zip=c74ab6c07ccb418c003d99a99d7d3b0c6b279207158d4f4c5d6d2e509744e4922e5951e1c56742fe7e1c449cacddde423cb9732123cc4709f5660a899548848d
commons-io-2.22.0-test-sources.jar=b984ef26f847c8bfe957e088c539b65e6936b97214e0d3f0be92b3b8164bd96a3360c410d113dbeaf4544ca6ce6c5ebc406227fa147988efb98d115373c4a46b
commons-io-2.22.0-tests.jar=8142d8c4d71b49c1f710cbf7890d9f9df49ac51ee733c2d701264aae07e56e4adbd0a5298129b403d84cbcc4b674df8061b2b5c02066ac6768a12cfa618d117b
commons-io_commons-io-2.22.0.spdx.json=2b41ff28958961453665cf233ac8a42678b129f1f5bdfb0bdd25b3e43ddd38e71a401f801bd8a0e72122853db538a262553654903a1287e4ee8126e1ea4bd830


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

openjdk version "21.0.9" 2025-10-21
OpenJDK Runtime Environment Homebrew (build 21.0.9)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.9, mixed mode, sharing)

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

Darwin ****.local 25.2.0 Darwin Kernel Version 25.2.0: Tue Nov 18
21:09:56 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6041 arm64

Docker version 29.1.3, build f52814d

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

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

JApiCmp Report (compared to 2.21.0):
    https://dist.apache.org/repos/dist/dev/commons/io/2.22.0-RC1/site/japicmp.html

RAT Report:
    https://dist.apache.org/repos/dist/dev/commons/io/2.22.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 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/io/2.22.0-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-io.git --branch
commons-io-2.22.0-RC1 commons-io-2.22.0-RC1
cd commons-io-2.22.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-