We have fixed a few bugs and added enhancements since Apache Commons Net
3.11.1 was released, so I would like to release Apache Commons Net 3.12.0.
Apache Commons Net 3.12.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/net/3.12.0-RC1 (svn
revision 78408)
The Git tag commons-net-3.12.0-RC1 commit for this RC is
bb741d0208786d1ef81ee417599396ffbb931d4c which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=bb741d0208786d1ef81ee417599396ffbb931d4c
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-net.git --branch
commons-net-3.12.0-RC1 commons-net-3.12.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1855/commons-net/commons-net/3.12.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Mon Jul 28 12:02:24 UTC 2025
commons-net-3.12.0-bin.tar.gz=6d3fb8a51357c08f0e6e8c138666cfad1b6acf221ccb3fa0e732434e1a7f981857f9b4101612c31eaabecd7a18cfce3ec7d750ec7db7f8423ff37d9810d0690c
commons-net-3.12.0-bin.zip=cd89b279d101ef698f9e456a89fe5b8d2ac3875df2d48e158b4995dbe64c85ee91157ce72ec89c257cc7d1801f091fa304fcc4acb378d5f269c8dce7c73442e8
commons-net-3.12.0-bom.json=737c7f96b6644598abc332c3d604a04e57983576e5a0b8849d009a5075400d1cc37d1f27d0be896d12b25dbcc86629141bc497c748303bb73617a45947a91e2a
commons-net-3.12.0-bom.xml=5ff7bd46e1397328a80a5eb4b29291ca9d92ef2d4e80dba636b6d879864da52740bce531aaa9ad0e8229660935f121e21a69abbec7d44363f632702183e93241
commons-net-3.12.0-javadoc.jar=b9f9aafe6398bb0c23720b9b6f0f6775501d2445784ba7e19c7b51e7dcc3fd74ec07ce8f6058ab6d2d0ce94ccaaf23816946d89a386bcbce44831f661dcc8be6
commons-net-3.12.0-sources.jar=de8090fd4e162994f27602e3187a0e1d48cf91c40f9d6650dfc0cd277be5e6fcf3b041f81767e1546506cac17e093d615411b77062e774aa2a3a8893b8b3bbe5
commons-net-3.12.0-src.tar.gz=f33da0d8f279a174e3c4eb4514a091a5ac74bd55067d6f230b268bab425fe92941f7322665c613ab2984c78dcc376cac5d665f966626108dd70604ffe682d149
commons-net-3.12.0-src.zip=8c78b23d55125eb818ab176f6db729691e3d605871412b51ffe38b175d0dc4efadaa091d546122d4bed0f1313cbd34d985e0ef5dc3871eb6f2eff9ec2407f16e
commons-net-3.12.0-test-sources.jar=53ac38776334783929d3a28df5894608a3d593299fd50b0d50362fed59de1c716def3b8caf9c5a6e81141b9d40f8aa780b33a312d5ec780c8eb55af2c0658d60
commons-net-3.12.0-tests.jar=9d2be32eb2f087918a2137c36be00a473099240e1d8420b260f523121b33e4b22518b6f8565f4ea38d7f26d1b75592035d6c8facc7fb52b7adfbe6e858902df5
commons-net-examples-3.12.0.jar=636f5da3338ae5601c6b9f90050908cdd60b4d07a2628d813044fb8608605402c623c0faca31ed53d2192a305a47a3fb1a8d76f5389c695419523fc84b2db17d
commons-net-ftp-3.12.0.jar=33b45b88bbd3167c2592ac82868cb912af13be681313680f6ef2f2daf7bf6153890532c08b7dfb5ad5183dfa748ba25f9d9a4f6d050f2c74bdfb66907a32004a
commons-net_commons-net-3.12.0.spdx.json=d11e2bfd5a2dc0ae9fbc3a3b8e15fb318e1b47dc9b66b414c270ad8bbf28d4a4206d05f1a70514e2e67acdac36ae277b69fdf6b531f5e075c4fd4edf2900a1be
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 3.11.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/net/3.12.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/net/3.12.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/net/3.12.0-RC1/site/index.html
(note some *relative* links are broken and the 3.12.0 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 3.11.1):
https://dist.apache.org/repos/dist/dev/commons/net/3.12.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/net/3.12.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/net/3.12.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-net.git --branch
commons-net-3.12.0-RC1 commons-net-3.12.0-RC1
cd commons-net-3.12.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-
