My +1 Gary
On Fri, May 16, 2025, 16:02 Rob Tompkins <chtom...@gmail.com> wrote: > +1 all looks good. > > > Thank you as always!! > > > On May 16, 2025, at 10:27 AM, Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > We have fixed a few bugs and added enhancements since Apache Commons Exec > > 1.4.0 was released, so I would like to release Apache Commons Exec 1.5.0. > > > > Apache Commons Exec 1.5.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.0-RC1 (svn > > revision 76868) > > > > The Git tag commons-exec-1.5.0-RC1 commit for this RC is > > 59c60c960aee9f10b9703dae3c63f76eac0fffd4 which you can browse here: > > > > > https://gitbox.apache.org/repos/asf?p=commons-exec.git;a=commit;h=59c60c960aee9f10b9703dae3c63f76eac0fffd4 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-exec.git > --branch > > commons-exec-1.5.0-RC1 commons-exec-1.5.0-RC1 > > > > Maven artifacts are here: > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1836/org/apache/commons/commons-exec/1.5.0/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Fri May 16 14:20:45 UTC 2025 > > > commons-exec-1.5.0-bin.tar.gz=f632d24030fb1975bd625701d2cbcad1e0ce210b0e65ff43198e2be58644f33b6858063badeda0387987e0a1383e5b87fd2419d850410d887053026c6f5bc50b > > > commons-exec-1.5.0-bin.zip=1acd58ee6e9e75f4ba76827d8053a193c8b6fa8eb1101da60b8f30cf5233c67af27ef2b555ff3aef5ce4fe51bf87f4ef584d25d801169ffaef16cc54886f74d3 > > > commons-exec-1.5.0-bom.json=0ebb61e6bdcee8e39dce9848c6a3f58d35a9f05d6b602d80f884593275b85e07d9c664339dc9418469f2c9eef3767f797cae302ff355d60dc2a990323aa59075 > > > commons-exec-1.5.0-bom.xml=b6a64ac12fe49c49f62022d53565b2aaa301740accbf676e49cb4cb805b134448cba61d0ee43207e2eee79957789f7c408ccda815d8f48064621da6ed84edfe6 > > > commons-exec-1.5.0-javadoc.jar=33629385311ac8baf384b8f4f2571abd1cac46814c3382fdad8c03abf145a18d2c790149b870492b965d83bbae01ac9ef770c6d2193c660e8a2f032fa255372e > > > commons-exec-1.5.0-sources.jar=f15b266416e4ca0ff8f3e0be434a9c43af54ed36fd6283cb7741b04cfe09f0979a33a280aa98b3e319a7596313180ccc3e49a66f6816f92694e8ae8a06cd13d4 > > > commons-exec-1.5.0-src.tar.gz=286841b38965612c03d3697fcb131ab8cd2ff0a065f8bbb7195c120ec36d8d930aadf36ce8d1a6693fdb321b67fa82ae052c9a87d4a5519717925b1cd176ae65 > > > commons-exec-1.5.0-src.zip=f9cf5ec14c5d886122a8870e9c13d69be92414db5f1db5e07b5cf4e7e90072badc748e943ff89530ea3250d82e65b4bd249700a088fc1bd2e85699ab0b00d73c > > > commons-exec-1.5.0-test-sources.jar=86fdf74cbd5394725add7a5d4323ddb9a543c9c980a2fb8cb14b1871dc3302233e4c1631b05c67c77d22ea48c1ffc5432089ca0799dc21936431cdfa329c3648 > > > commons-exec-1.5.0-tests.jar=705ac1e293fa5a50f899cd0de42d776cda4afa7364e323d654911edecef6b155969333de535561161ad6c10a86bac137828f952ec44f85aa9e3c3cd99db6757a > > > org.apache.commons_commons-exec-1.5.0.spdx.json=19e6a16d6d6374f7a971052095a6c1eb9d28c785ea7e389132965d610e0c5b40a36bb29880cc8abeca2ea27caf52a2ae224b732e012d4186fd257b854a6ec4f6 > > > > > > 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.4.0 are in the release notes: > > > > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.0-RC1/RELEASE-NOTES.txt > > > > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.0-RC1/site/changes.html > > > > Site: > > > > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.0-RC1/site/index.html > > (note some *relative* links are broken and the 1.5.0 directories are > > not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 1.4.0): > > > > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.0-RC1/site/japicmp.html > > > > RAT Report: > > > > > https://dist.apache.org/repos/dist/dev/commons/exec/1.5.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/exec/1.5.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.5.0-RC1 commons-exec-1.5.0-RC1 > > cd commons-exec-1.5.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 > >
