We have fixed a few bugs and added enhancements since Apache Commons
IO 2.18.0 was released, so I would like to release Apache Commons IO
2.19.0.
Apache Commons IO 2.19.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.19.0-RC1 (svn
revision 76142)
The Git tag commons-io-2.19.0-RC1 commit for this RC is
2186f41bbae123ed355a77137e9be10c0b4c4630 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=2186f41bbae123ed355a77137e9be10c0b4c4630
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-io.git
--branch commons-io-2.19.0-RC1 commons-io-2.19.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1817/commons-io/commons-io/2.19.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Tue Apr 08 22:05:39 UTC 2025
commons-io-2.19.0-bin.tar.gz=447500ae140b6d9ef2fa69019c053b0d1780daa9ffa1d486fa4fb2daac045244d9ea747a6292ea5b605e18cf0688100a48861c01fee560545624f8001ffc9a01
commons-io-2.19.0-bin.zip=282bdb2cd5ff9417434321ffc2eb8f3dd5d1fe96f38bd27a9f35c49692fffdae93effb2fe529b98790dac6723a7e0d5cc3587564a47fd289133162c5343db574
commons-io-2.19.0-bom.json=081e1ab234128a1861180ecf07602f68f575d751f3989604b06325863bf235009834e2da6d09bc662920920fd63fa82822c162a58a3c661244c2ffa3dedf3fba
commons-io-2.19.0-bom.xml=0be3270900666f413542a7e2291772a2b72975cf10fecbbd54dd4e6699acbf90c93d9cfb575c368753c7460ecb765ab38515260ca2fcf9b4095acb32b056164c
commons-io-2.19.0-javadoc.jar=7c4fcca9e32b2863a1eae8b31ef7934305ede42be502db5591b860e436901335b6316ef65f0e510cc1b4715e48c795dfc2f28b9a44fd0647a94cb172eb373185
commons-io-2.19.0-sources.jar=fe4b997848ccd1c3954cb37b0ab766f19d8e01fcc1f7b3aa4cabe0218532f346fb425f5fadd62963e3f86361a1aba97a005705b64857ce8665360c6c9fa531e9
commons-io-2.19.0-src.tar.gz=217e711d2d0716b0b1fb858322a041b3d7ffb50e32adfad02681db966e453adb254b3d41123070d07a1883d050f250e253c084275af7782223ad7e48932be7e8
commons-io-2.19.0-src.zip=62c805181e587f4062e1f33b9afbb273868c183fbe7ab8ed735873703ad329b95a5b564969c73b9e352028215942352ae6c2337c6b93df3e0656c53fb178c68e
commons-io-2.19.0-test-sources.jar=c9dfebeb7359d4ffc1bdc56790e9397e1320328fdcd9b96abdb7476b15b9549bdfcacec836049d142d44746a691cc5ea9c3db321ff88a77644eacff695abd995
commons-io-2.19.0-tests.jar=adb2bb0b3636fbb66978883103da549adeccfcdd0e0a681eb70c77b38d8ba4f272ed03a8bb598c9897f2e42cd38b3471d40e3c193b66b28be2b1773e5b49ae97
commons-io_commons-io-2.19.0.spdx.json=3c23078c5a63e0806334f2b6799a95844966ee3a4bb3794bec94a7b2923309081d06409a99c1fe5c26f0ead7d244e618da629f42ec4d5aae3b744c255c1837d5
I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy
-P jacoco -P japicmp clean package site deploy' using:
openjdk version "21.0.6" 2025-01-21
OpenJDK Runtime Environment Homebrew (build 21.0.6)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.6, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec
Java version: 21.0.6, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.4", arch: "aarch64", family: "mac"
Darwin ****.local 24.4.0 Darwin Kernel Version 24.4.0: Wed Mar 19
21:17:35 PDT 2025; root:xnu-11417.101.15~1/RELEASE_ARM64_T6041 arm64
Docker version 28.0.1, build 068a01e
Details of changes since 2.18.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/io/2.19.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/io/2.19.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/io/2.19.0-RC1/site/index.html
(note some *relative* links are broken and the 2.19.0 directories
are not yet created - these will be OK once the site is deployed.)
*** JApiCmp Report (compared to 2.18.0):
https://dist.apache.org/repos/dist/dev/commons/io/2.19.0-RC1/site/japicmp.html
***
Note that the above report notes several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.
Errors reported:
- methods added to interface: OK because that does not affect
binary compatibility.
- etc.
***
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/io/2.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/io/2.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-io.git --branch
commons-io-2.19.0-RC1 commons-io-2.19.0-RC1
cd commons-io-2.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
