+1 all looks good to me signatures all loook correct, the site looks good, the reports all look good, the work underpinning the release looks good. builds on 11,17,21,25. Release-Notes good too.
Go > On Jun 20, 2026, at 10:53 AM, Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since the release of > Apache Commons JEXL 3.6.2, so I would like to release Apache Commons > JEXL 3.6.3. > > Apache Commons JEXL 3.6.3 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2 (svn > revision 85346) > > The Git tag commons-jexl-3.6.3-RC2 commit for this RC is > 22c9343c1221b96f9c452ca35a657873610a05c8, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-jexl.git;a=commit;h=22c9343c1221b96f9c452ca35a657873610a05c8 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-jexl.git > --branch commons-jexl-3.6.3-RC2 commons-jexl-3.6.3-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1950/org/apache/commons/commons-jexl3/3.6.3/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sat Jun 20 14:43:52 UTC 2026 > commons-jexl-3.6.3-bin.tar.gz=5d218237d78a2844456a9f290465aa01ab9634221a8bdaba4e6dc6954fc1c661cf8009b0b75bd4112a84532da8585af8b76e92f56cd853e81b635f99e86c279b > commons-jexl-3.6.3-bin.zip=5b6be2aad828824f1bf00dede1688cbbab5001c8d4f42cd781c462e2a7ec252a9f934c2e45d055580c92e2670eb9d3576733a1219783cb6fcf4c55f3d261d3a9 > commons-jexl-3.6.3-src.tar.gz=1fec6494a26bcb2c98d25a644f1fc3c59af733a5c71022b816fb4a65a9356a1f3a67639b7ca037df24fc9bb6aa6c249c3e83bc94489531b6f629ebfe13739f3e > commons-jexl-3.6.3-src.zip=0a1204d1eb6647707574b4c2e6be47c390cdef59af4c02cf51313bdd6dd72dc58a3a994fad23c8d7bcf9f4e1ac042f25f5d6c1f541e9fe7eb733f9043bb89fe6 > commons-jexl3-3.6.3-bom.json=476d36bc338fd408b71f6cc92ea83008fc1588a803b5e9b2928b30cac7bb732c483f3fbb2bf4c3f268f3c13a73cf03a8156c7cc92337ce818e4523f09ea47df7 > commons-jexl3-3.6.3-bom.xml=a7adc2e32dc6a60aae5279fce8a137055232712f66c77adca83f1ff0a2765c204d0256f1fea20776d54684a1762082a6c163b3cdf43e04208924b25c4fd6454d > commons-jexl3-3.6.3-javadoc.jar=ade7659986bb50035c2abe8a963de757928dc8f6b5d843cb9b5045163128ea6e84cbee350ac407863a5e36cb888b43e78f8786755de29399ea88e5f8a9dafb9e > commons-jexl3-3.6.3-sources.jar=4d2967a30ca7c4389ad5f7cf0001654e8f6607da370b2699078541057f22a3d22a5b0cdb5ac03508cea656f350147467922a8bccdb2f783c6aaab2d205c59549 > commons-jexl3-3.6.3-test-sources.jar=55d98a4afb526c211475865d629df369a06616dded2bae8a32550e7c231c5afbea00464da74f16cdd1a2a736ec8db9ca9f10e6b4dafb74a1779f801519dfc436 > commons-jexl3-3.6.3-tests.jar=9557d9ae7342474e493f0abbb6c9267ac10968de51fc4b417be20b53e29a09a6f4a7fd0c8cb4864ddf1eec59185ff87c3a61a808d564ce2beafb1318e1dca6e0 > org.apache.commons_commons-jexl3-3.6.3.spdx.json=5c0cc93e95a366f250619196a797aa15083d0c6e7f24ea9e63f249e5c4f0bd81f5173305bc7076b7900e6ca3e18573bcc357196a8e0aebd3994846d4f2949045 > > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.11" 2026-04-21 > OpenJDK Runtime Environment Homebrew (build 21.0.11) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.11, mixed mode, sharing) > > Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) > Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec > Java version: 21.0.11, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.5.1", arch: "aarch64", family: "mac" > > Darwin Garys-MacBook-Pro.local 25.5.0 Darwin Kernel Version 25.5.0: > Mon Apr 27 20:41:15 PDT 2026; > root:xnu-12377.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 29.4.3, build 055a478 > > > Details of changes since 3.6.2 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2/site/index.html > (Note some *relative* links are broken and the 3.6.3 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.6.2): > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.3-RC2/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/jexl/3.6.3-RC2/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-jexl.git > --branch commons-jexl-3.6.3-RC2 commons-jexl-3.6.3-RC2 > cd commons-jexl-3.6.3-RC2 > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
