We have fixed a few bugs and added enhancements since Apache Commons
FileUpload 1.5 was released, so I would like to release Apache Commons
FileUpload 1.6.0.
Apache Commons FileUpload 1.6.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.0-RC1
(svn revision 77391)
The Git tag commons-fileupload-1.6.0-RC1 commit for this RC is
f3e030f09ac8b01b684466c793dec86eafe1e4c9 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=commit;h=f3e030f09ac8b01b684466c793dec86eafe1e4c9
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-fileupload.git
--branch commons-fileupload-1.6.0-RC1 commons-fileupload-1.6.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1840/commons-fileupload/commons-fileupload/1.6.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Jun 05 15:19:04 UTC 2025
commons-fileupload-1.6.0-bin.tar.gz=d63130adbeb48b9a2420bc98d35f0e621190c4c763004bb30d624f58b13c255d3492ffc9b8deab92a39ca4039987544feb081b6acc6da472a463f2dd13b85725
commons-fileupload-1.6.0-bin.zip=1507e0887432cf51a5ee2dd24bf26c40dfa085735cf8402a745accf6c2538b1e8461b5fa01c727ba7b45e8f4c75279b25b3f79861a4b5a19f7a396b8153d1bac
commons-fileupload-1.6.0-bom.json=b69f091e203cfceae08d919fd968e75c00c0fcf1729de22781d3d1af005e470ed95c809c447dcf7721297f736d4de65374a237f7632cce7572fa42791f20bf43
commons-fileupload-1.6.0-bom.xml=7c14f23abd53776fe2491a1488acd0311f944d1606098e0405ef43c49a2a4f07d56f6ab56e60214e9f8af2b5df225e3f5ab0edff4f2fdcdf51007b5d4b370c29
commons-fileupload-1.6.0-javadoc.jar=82b5bf6cf19775acee050e3dd842213ffd9b6f137d45e53b789080a4d068807fb646f32404d97ee4370307cf93a401f65e7d83be1324a698b5ef100e8060fb82
commons-fileupload-1.6.0-sources.jar=e53f82560b2f783ff0e335907efbe5da4d824833ae3e0d16013dd98f39a6a20642caeaf4e60eae4c74f2e5b6af3f505f54d2174bfdc2f11c11b6f14164acef19
commons-fileupload-1.6.0-src.tar.gz=af6b8c38e93ea61bf4a7da4597c2a81b653552647fe422f59a0a335a9358d8c7f80a50f183170a537b360b739599f7e3e9ea08bbbdd687a07e33f6bb5261445d
commons-fileupload-1.6.0-src.zip=e493d5a3b76200e8cb89e385c37f33c81579e07a567f435148b400e2448670617ed6e5183d878ff5e610bcea26fb775a2e7a0487803235a5ce60c551eb3a1f11
commons-fileupload-1.6.0-test-sources.jar=406b530dd899fa40b76ed92c2f00a29dae8891a435d18e7de4db3a206c05bab9027707fecf76deb7e72396ac248549e7d8ac078abae4d23e95c27185e23ea009
commons-fileupload-1.6.0-tests.jar=4e029ee689cf4302f9b92b20c159b9e88f87a3491d44f8f6b752f233d2228fe2ca9602a114dd713289d2d107e713cbf2209d302711e93876be92581cce165dec
commons-fileupload_commons-fileupload-1.6.0.spdx.json=05684779139a10a86a09e8549ba06e9bfb0e404e1be52b913953bfe46b73bf49f9a75325cfbeb46daa7dc70da0e44d687fbd3fb7ac47b6cf58eb32c99735b40a
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.7" 2025-04-15
OpenJDK Runtime Environment Homebrew (build 21.0.7)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.7, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec
Java version: 21.0.7, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.7/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 **** 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.0.4, build b8034c0
Details of changes since 1.5 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.0-RC1/site/index.html
(note some *relative* links are broken and the 1.6.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.5):
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/fileupload/1.6.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 24 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/fileupload/1.6.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-fileupload.git
--branch commons-fileupload-1.6.0-RC1 commons-fileupload-1.6.0-RC1
cd commons-fileupload-1.6.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
6) Build the site for a multi-module project
mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
Note that the project reports are created for each module.
Modules can be accessed using the 'Project Modules' link under
the 'Project Information' menu (see <path-to-site>/modules.html).
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
