We have fixed a few bugs and added enhancements since the release of
Apache Commons Exec 1.5.0, so I would like to release Apache Commons
Exec 1.6.0.
Apache Commons Exec 1.6.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/exec/1.6.0-RC1 (svn
revision 81054)
The Git tag commons-exec-1.6.0-RC1 commit for this RC is
b4d857f9d11ec28a435e025fedd70bfc06583da8 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-exec.git;a=commit;h=b4d857f9d11ec28a435e025fedd70bfc06583da8
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-exec.git
--branch commons-exec-1.6.0-RC1 commons-exec-1.6.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1885/org/apache/commons/commons-exec/1.6.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Nov 27 14:06:45 UTC 2025
commons-exec-1.6.0-bin.tar.gz=60dc9f43743b470ebcc5293773f0b166d2213f151180018a545fdc4076f7e8f38fa8c094ea56f4846bf10636d57a520f274f693a38d8ff7adcfe77b584c22e91
commons-exec-1.6.0-bin.zip=7ec4f93d25844de51a01069e2753d60a572afcda85520d8f775ae2a86febcf78261b6ff0a18258f619293bac8333452783a32436941d49c5366551175002097a
commons-exec-1.6.0-bom.json=b8a04c248db32ddfab5e65e5120edf837bd975d8e8cee0f05ff4e841be90e349ec24e0c46f0db227cafdfda441dc40bf9a9c9f185dd3cf5610ce0050051f28fa
commons-exec-1.6.0-bom.xml=4183dd03439cc94c5d35f66a3d22f0a61428587a04c688c64070d56df10754a247f316b7c2f08b61ed98fd7179d81724d0de2cdb0d3d66e09b42ec5bc2367f7b
commons-exec-1.6.0-javadoc.jar=5dd08b992d51f5b11fc9889008c23d93d2d3111c282a567589f4f25a4590c03284e02c329d16c0268d43f803bf65cb7380b13b0983b0ddfb974304a96a5ea9e6
commons-exec-1.6.0-sources.jar=b4d3f66f1f748f1efc5cf641fabf4cafc6f43d7ef98b5dd3290c887fb6791cf2950b6804af87964e48927ae573592a82611019bfd33a59f2067ad6a653576965
commons-exec-1.6.0-src.tar.gz=00e8eb552e886ba9da0b9636ee9ffce142eb33faa9d2873e7619e6508ab59b214bde1818f43012ecdab928ddc0697514482b33c3c268729c3049ce4306a7ea1e
commons-exec-1.6.0-src.zip=0c467df9b5629f6c86691fa7fad77424e8208ad7337aca2a166a49cc4a6c8b77d987c20f2e710248ea9dd6b0af7098ab78088d516138e458ff27d4fa211272ee
commons-exec-1.6.0-test-sources.jar=0c8d634df4bd107792d759bc82aaac2829773b03193f299f75c7d10497b6712490646995a8ed9507a86e7ea679cb2e12d8c7d9742de1616eec4f1c3f22794f71
commons-exec-1.6.0-tests.jar=d177b8576ccf2ec796ad8467c700ebcbeb5335cc7597923ba57715a13526ad5e90ef2cf3d0fdfd2fb9c57aa2b783ebb8a877b703685d77db277db104ddf7e064
org.apache.commons_commons-exec-1.6.0.spdx.json=25628ecb073b7bddc8ac6ed6f9dee65002a9863939b710d39d4c1366d9d80251fe976fcc8bd790412af9e743edb7f05fc697092d79c353e137d48f303b39af24
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "17.0.17" 2025-10-21
OpenJDK Runtime Environment Homebrew (build 17.0.17+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.17+0, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 17.0.17, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@17/17.0.17/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac"
Darwin Garys-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0:
Wed Oct 15 21:12:15 PDT 2025;
root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041 arm64
Docker version 28.4.0, build d8eb465
Details of changes since 1.5.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/exec/1.6.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/exec/1.6.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/exec/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.0):
https://dist.apache.org/repos/dist/dev/commons/exec/1.6.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/exec/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 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 530AA5F25C25011F)
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/exec/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-exec.git
--branch commons-exec-1.6.0-RC1 commons-exec-1.6.0-RC1
cd commons-exec-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
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
