We have fixed a few bugs and added enhancements since Apache Commons
Imaging 1.0.0-alpha5 was released, so I would like to release Apache
Commons Imaging 1.0.0-alpha6.
There are many Javadoc warnings, the Javadocs are still a work in progress.
Apache Commons Imaging 1.0.0-alpha6 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-RC1
(svn revision 76527)
The Git tag commons-imaging-1.0.0-alpha6-RC1 commit for this RC is
1fad84c74af3be111a564b8aba24dffc7e14b580 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=1fad84c74af3be111a564b8aba24dffc7e14b580
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-imaging.git
--branch commons-imaging-1.0.0-alpha6-RC1
commons-imaging-1.0.0-alpha6-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1833/org/apache/commons/commons-imaging/1.0.0-alpha6/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Apr 27 15:26:14 UTC 2025
commons-imaging-1.0.0-alpha6-bin.tar.gz=820e694cba60e4b1fc8770bed935fd56125565a3a9e1bd5ac38c2ec461eaf621fb14faedb446d3b59e2c85143b8e6903eabc4e5f1f62cae292640bd4f627f234
commons-imaging-1.0.0-alpha6-bin.zip=283fa5241edb5b6e68224368779b67da0a11dcd79089fe81bc6a3dbe59db93664aaca2a0ca3ef7a1f3936119a6a9c08421b4f4cd563f77e5d2f162723c7b5ec7
commons-imaging-1.0.0-alpha6-bom.json=0225049ff9d5824a6adfd67fd41f0b29d15f061629571d3934d94a22da39d98f7f5f27f2c6552a0accda83d6be0406a94638d33280e50ec680699ad528c7a255
commons-imaging-1.0.0-alpha6-bom.xml=75b72e59b30592346c0e38f4163af6281eba0214d11b0f5991d53e4aad153f90e3cd1bb3433555b8f3dac09459c4885b8b5a8a4a1d4ffa8095cf80712e1ad0c5
commons-imaging-1.0.0-alpha6-javadoc.jar=04c6b808d8cecd39630f9fae73be3b1f89b381f9ed650c24326025021be34546bfbf79be4771b27c4c0b65e1acc440dd496bf75c14d84397b3ef6fa90bb2d883
commons-imaging-1.0.0-alpha6-sources.jar=7d9aa9011af3d49db434f87e974df0382c66c9d4b7dbcad66e469feab37c3b54e9dc94be07157f9dc60e66d3ee172ff44ab255d6d24a29ddf7262654ea657119
commons-imaging-1.0.0-alpha6-src.tar.gz=94764a7afa773f6db75aaae21551a58a3d362fa9221a5f52f07e88e24a101513e066a7897b1817ee5bfb051c91f41386fd1e7289528f7cc4c09b267e463993dc
commons-imaging-1.0.0-alpha6-src.zip=2afcfe1a2732f7731a9c669583dc593daf1b6f38426757d9df380123085c083ada68c0d2954854f288d7729c619a8282213920cc8ecd04f74975d4e9dd7f2022
commons-imaging-1.0.0-alpha6-test-sources.jar=fed1f12834283d1d87c9e6060fd4859b527434da0514025be71aa5415d66eeb420d89e9f1417ff21c188fe2b2468d426173d93cb2c9af2f205b44e1bc417da7a
commons-imaging-1.0.0-alpha6-tests.jar=2dc6773cab135d2dfb192e0c2ae39ea1f79fd5fb0b141e3db51714f36e0f210e293506b0fca0e5f5d743c567f03052554a6d80434ef6e76c7496a5cd65aa188f
org.apache.commons_commons-imaging-1.0.0-alpha6.spdx.json=f1d3dfcf5722abee4ce66800caeb170763f1255c8d6b77ae6f9ed18aed63c03cf2f94899f8ed988a85c1ee563e7c24040ccd83d854e3365d207d51b1715bba63
I have tested this with 'mvn -Ddoclint=none' and 'mvn -e -V -P release
-P test-deploy -P jacoco -P japicmp clean package site deploy
-Ddoclint=none' 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.4.1", arch: "aarch64", family: "mac"
Darwin Garys-MacBook-Pro.local 24.4.0 Darwin Kernel Version 24.4.0:
Fri Apr 11 18:32:50 PDT 2025;
root:xnu-11417.101.15~117/RELEASE_ARM64_T6041 arm64
Docker version 28.0.4, build b8034c0
Details of changes since 1.0.0-alpha5 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-RC1/site/index.html
(note some *relative* links are broken and the 1.0.0-alpha6
directories are not yet created - these will be OK once the site is
deployed.)
JApiCmp Report (compared to 1.0.0-alpha5):
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-RC1/site/japicmp.html
This is still an alpha release, there are API breaks like renamed
classes, see changes.xml/release notes.
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha6-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/imaging/1.0.0-alpha6-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-imaging.git
--branch commons-imaging-1.0.0-alpha6-RC1
commons-imaging-1.0.0-alpha6-RC1
cd commons-imaging-1.0.0-alpha6-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
