+1 all standard checks look good. Reports, changes not too profound. Signatures good. Builds on 8 - 21. Site looks good, release notes look good.
KEEP UP THE GOOD WORK! -Rob > On Nov 8, 2025, at 7:03 AM, Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since the release of > Apache Commons JEXL 3.5.0, so I would like to release Apache Commons > JEXL 3.6.0. > > Apache Commons JEXL 3.6.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.0-RC1 (svn > revision 80572) > > The Git tag commons-jexl-3.6.0-RC1 commit for this RC is > e32160b71c3d571618265813caaadc834ab956b8, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-jexl.git;a=commit;h=e32160b71c3d571618265813caaadc834ab956b8 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-jexl.git > --branch commons-jexl-3.6.0-RC1 commons-jexl-3.6.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1873/org/apache/commons/commons-jexl3/3.6.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sat Nov 08 11:50:23 UTC 2025 > commons-jexl-3.6.0-bin.tar.gz=acd73b047820e7eab400d4a0f6e416a150784c95a12875522583bdd85fdcda92393405579c128f15a327fc177f7a21403c7b930a602534969070329e365bd07e > commons-jexl-3.6.0-bin.zip=916743c2df31ad839b000337e2f453d5178db70e533c2990193876a2493ec18287871233d2d2581a94b496f1fcacc6b0ed3f5e1f729377463ee438ff9d48d031 > commons-jexl-3.6.0-src.tar.gz=74cf4cf34d0bcbe5b97651107347336ff5315251cf09e8978586494a8dce6fc853bf0ccc12483fba2d5dd4263b68cc57189ff07f8a96751a6fab0c06395cebbe > commons-jexl-3.6.0-src.zip=8e4409d25600db1848290a16f3ce54a3aa55b3a060f9533856e7d7b2b1bfb9f523084a6677af27358f32e6fa6f0acf33d2c1e340ceff9a9760479f3280115ed2 > commons-jexl3-3.6.0-bom.json=f5c24bccbf701e12ff4d9d67ac2454959c07aba0dadee1d266c296d30b9ea2c940f62b9ad16f5f7a98a35d234907703994e4442a6cd44a34bd55b4d049373a56 > commons-jexl3-3.6.0-bom.xml=4c0ed63084228ef9648537880bb2551f9d31a0900ddca9338c8cf47c9e86bc3ed8c2eadb346e1c647c3d574e60f7a47245c2f1e69b9cd8ff0af743defd26a585 > commons-jexl3-3.6.0-javadoc.jar=fdf7710512a5ed53e83d1a4aae6e35aa05b1e1ecfdfafbda1f7c9b3f0be7804e08716a7a891a9c00810036d4236c03f0dfedb911cf969fe7c4e69cab51c68666 > commons-jexl3-3.6.0-sources.jar=39a7850ec12166a047de79bc0d29bc68fdbbe77dc8281694aff56b1f11cba0db2fc8b6e9d91cf478bc77511d65b7b48d354bf83f6bd2f02a488ea577e00cf7cd > commons-jexl3-3.6.0-test-sources.jar=59660696b7ed64f5d2cff17832af27c26ba38578e64b3872901c0284ce9741fd754517f04d00a7daf81026c24a3543384d6dcf4ff20b2eb5b995304f1c7711a6 > commons-jexl3-3.6.0-tests.jar=b07c04899ecdb23d1478a3a4b4af597cdd7269b029c910516d86a92820562e4259790376bfd3736921ef3b7ab933eb4b7c042f56aaca39485b5dffb7fe893db3 > org.apache.commons_commons-jexl3-3.6.0.spdx.json=b79de1de94a72a87a8453ef63c1ce6afea735e4c09893957a2cb23dfc44b5d6b95010e454f5bfb8c7bc34e50068e11a7d13ed85c4d431b01c8ddd423dae6c2a5 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "25.0.1" 2025-10-21 > OpenJDK Runtime Environment Homebrew (build 25.0.1) > OpenJDK 64-Bit Server VM Homebrew (build 25.0.1, mixed mode, sharing) > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > Java version: 25.0.1, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk/25.0.1/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 ****-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 3.5.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.0-RC1/site/index.html > (Note some *relative* links are broken and the 3.6.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.5.0): > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.6.0-RC1/site/japicmp.html > There is one oddity reported by JApiCmp where it thinks moving a > method to a super-interface is not compatible: > In the previous version 3.5.0, the interface > JexlContext.ClassNameResolver doesn't extend anything and implements > resolveClassName(String) > Now, the interface JexlContext.ClassNameResolver extends > JexlUberspect.ClassNameResolver, which implements that method. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/jexl/3.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/jexl/3.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-jexl.git > --branch commons-jexl-3.6.0-RC1 commons-jexl-3.6.0-RC1 > cd commons-jexl-3.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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
