[VOTE] Release Apache Commons BeanUtils 1.11.0 based on RC1
We have fixed a few bugs and added enhancements since Apache Commons
BeanUtils 1.10.0 was released, so I would like to release Apache
Commons BeanUtils 1.11.0.
Apache Commons BeanUtils 1.11.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.0-RC1
(svn revision 77116)
The Git tag commons-beanutils-1.11.0-RC1 commit for this RC is
9c0b5cf007818c3fb1ac36d5ed394d56d0fd13c3 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-beanutils.git;a=commit;h=9c0b5cf007818c3fb1ac36d5ed394d56d0fd13c3
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-beanutils.git
--branch commons-beanutils-1.11.0-RC1 commons-beanutils-1.11.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1837/commons-beanutils/commons-beanutils/1.11.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun May 25 13:18:42 UTC 2025
commons-beanutils-1.11.0-bin.tar.gz=c1c0e71f526db64fc7aa9934f2910eedea5e575909edb3de39566e9a27b300e28826f6997b23338ef93dfee34d220077ba8669459640bddf5619ca0bb740d8ba
commons-beanutils-1.11.0-bin.zip=ec11bd2a16255a67c7a450357c8e7cab5e85dcfdb279209685c2e9cad338b316f1e6a5e48fffa4fe4057cbb51962a3c52265ee868f87a9a50b7196b7a86af464
commons-beanutils-1.11.0-bom.json=8fd1cc40ae809cd088580e398c1ddcfe69b8fcb81db8a9e6cd7352d3e7be1c42599f314c1153d6770f0a87b0b99e6e49c24ab1c6cf299de4e641ac58d70e5635
commons-beanutils-1.11.0-bom.xml=6437cef8199d41717f367bb844cc1ad8ffd62575d8edb354b10d9ad8f1960a205d71661e8bbe9ff4f2bc74f86cecfee955540fcb6374d62a777f4119033fdc21
commons-beanutils-1.11.0-javadoc.jar=53f38cf856c5fb95f7530486c06cba396aee326a700ff29f75b0ce41dc1e1df94a65ad5f75b85154f1d6a54175902bb9e137843e55e8b1e7553f21b282cd1dbc
commons-beanutils-1.11.0-sources.jar=ac0eea3c80b59e7293968bb502aecb61a89498506c98f86f2e61b1265b275a061b3e7983009466135e4db8ee3e921f62f87c483b0067473f5a158e0bde1cd3c3
commons-beanutils-1.11.0-src.tar.gz=edd930e7f8118d0cceb8647666fe1d5f873f939f858f433cd19985a75c4575455f2a2d339e4bcbf08b3f586c785a60429d4bb33ff6239da8f2c6183c8c318f18
commons-beanutils-1.11.0-src.zip=2c0796738ed7662840e3cda12007488b88f0b80679e7e0e6f64a8402a5dad92ce810f9648c9e86b8a3754c74e7a1a03e24eb189a12d6bda0e2b023b9e2405aaf
commons-beanutils-1.11.0-test-sources.jar=402f555f768f58c638778c15aac51326b42536a9a9b1bde5f91808acc43383808aa3c212154ae20d594528f201ada51e3e1e8be63a9405151d8239b9db747a12
commons-beanutils-1.11.0-tests.jar=27b0084bdf5e897d847520f7541d5e4fbea96356ee573fa326a9965ca8a9c67bc0bb1b5b6d2574af276c14e850e669bbc360394f032286f4a822970964557e12
commons-beanutils_commons-beanutils-1.11.0.spdx.json=7cfd3bc8747ca726254e8661f517b7ae4502c34bdba8dbab4ddf61041d5e175d24f825f5fdf17319258c850a2b1ef535bfa9ea7bd1991a9b38273918b9f3f67e
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 ****.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.0.4, build b8034c0
Details of changes since 1.10.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.0-RC1/site/changes.html
Site (will not be published since 2.x is the published site):
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.0-RC1/site/index.html
(note some *relative* links are broken and the 1.11.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.10.0):
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.11.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/beanutils/1.11.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-beanutils.git
--branch commons-beanutils-1.11.0-RC1 commons-beanutils-1.11.0-RC1
cd commons-beanutils-1.11.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
