Re: [VOTE] Release Apache Commons JEXL 3.7.0 based on RC1

+1

> On Jun 28, 2026, at 7:10=E2=80=AFPM, Gary Gregory =
<[email protected]> wrote:
>=20
> For those of you following the bouncing ball on various mailing lists,
> this feature release should put the cap on the recent string of 3.6.x
> releases.
>=20
> We have added enhancements since the release of Apache Commons JEXL
> 3.6.4, so I would like to release Apache Commons JEXL 3.7.0.
>=20
> Apache Commons JEXL 3.7.0 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1 (svn
> revision 85502)
>=20
> The Git tag commons-jexl-3.7.0-RC1 commit for this RC is
> 21827925ba6f4fff46ffe4c1f6c4fd41abc663a9, which you can browse here:
>    =
https://gitbox.apache.org/repos/asf?p=3Dcommons-jexl.git;a=3Dcommit;h=3D21=
827925ba6f4fff46ffe4c1f6c4fd41abc663a9
> You may checkout this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-jexl.git
> --branch commons-jexl-3.7.0-RC1 commons-jexl-3.7.0-RC1
>=20
> Maven artifacts are here:
>    =
https://repository.apache.org/content/repositories/orgapachecommons-1952/o=
rg/apache/commons/commons-jexl3/3.7.0/
>=20
> These are the artifacts and their hashes:
>=20
> #Release SHA-512s
> #Sun Jun 28 22:55:18 UTC 2026
> =
commons-jexl-3.7.0-bin.tar.gz=3D5ebbf8e30e6e42b2dda716c10b6a7c6156fb3cf63c=
e6c1f66552b541469cce707ad0d2ab82fb17bda184623b7fcf590bd58f25d621a8a82997c2=
7f7c8a360445
> =
commons-jexl-3.7.0-bin.zip=3D9681e21626b46d7e7a4c4e828ba18dd704a3b9db61e4e=
82cf1f6edfbb9ec678c6098204b9a8ccfaffd5738306792e170c0268f77c42ed5382e5eec9=
2ac8f17c7
> =
commons-jexl-3.7.0-src.tar.gz=3D710b7d2cb5820621b26ff52dadbfa107b2394ac5e0=
046e3004f35e1af6a065babaa1bbfb301c4f06ad949e15634631cf10abde9e963cdd41dc4e=
304343adb418
> =
commons-jexl-3.7.0-src.zip=3D16c2d884de119f0f84cc22efa6c013318875e1f801206=
3ab21d0d2663dea7b099a312e983a2aa62dce2490b2221fa3eea6cd536c524fd95f7d81fa3=
cd396f8f4
> =
commons-jexl3-3.7.0-bom.json=3D0ffd588566c846e96171f07aded54412d6a29dffd39=
c2c54e03e59c664ca2e02b1b3e0005084aa4cfb2da57b7bdabfd460f4b367179f21463514d=
25b9bb3e122
> =
commons-jexl3-3.7.0-bom.xml=3D5468ad1cc20a8b57a9b295707dbb7b6e51a0d8fbf4a4=
04cd91403b6c5736ba90cb7b6ae3f5e56d03c647490842bbdfa2c15bee77314a8d171b4fc5=
294110ea37
> =
commons-jexl3-3.7.0-javadoc.jar=3D9f5511730238e260f4b1794d6adf506ceeeff541=
16a8cc86129f8294bccf8f97e8c024b087864d23ff71db031a6bf28f1503588152c3015bdf=
2ddc3aefbb0448
> =
commons-jexl3-3.7.0-sources.jar=3D94e440855fe18e78311097a19e208fc73a4d6f34=
5e3f1b7100d44545ee9633066855bbe068e2f101e0235f7ebbfda232ee3538d9fc057b1a3e=
37088a5f14caec
> =
commons-jexl3-3.7.0-test-sources.jar=3D4cafddf23c7b1e3f49eb03f6c33865f04ad=
e050f90ed285bf6e048e99ee34afc00aeb8d62d81653f23c241e3f70dd08c57f219be5a152=
082fb7ea45a9d6bbb92
> =
commons-jexl3-3.7.0-tests.jar=3D07b1d140fbae58769588539fa2c9e1e0bd57e8aedf=
febfd29aee18e20f6e4dea9048f785aedbc0276663a2cb9ecb050c1b3f18318fa30b2cadd9=
18e32be227ae
> =
org.apache.commons_commons-jexl3-3.7.0.spdx.json=3Ddd6bdb07be5fe9a4056d949=
b4300fcf55a8f66eb8eae8f99b429d93fc354ce90016c5898caa6094eb6b2bbfede89b29f7=
f83d7ed0affb2cc8f99f7af48154b9d
>=20
>=20
>=20
> I have tested this with 'mvn' and 'mvn clean install site' using:
>=20
> 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)
>=20
> 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"
>=20
> 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
>=20
> Docker version 29.4.3, build 055a478
>=20
>=20
> Details of changes since 3.6.4 are in the release notes:
>    =
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/RELEASE-NOTE=
S.txt
>    =
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/site/changes=
.html
>=20
> Site:
>    =
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/site/index.h=
tml
>    (Note some *relative* links are broken and the 3.7.0 directories
> are not yet created - these will be OK once the site is deployed.)
>=20
> JApiCmp Report (compared to 3.6.4):
>    =
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/site/japicmp=
.html
>=20
> RAT Report:
>    =
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/site/rat-rep=
ort.html
>=20
> KEYS:
>  https://downloads.apache.org/commons/KEYS
>=20
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
>=20
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
>=20
> Thank you,
>=20
> Gary Gregory,
> Release Manager (using key 530AA5F25C25011F)
>=20
> The following is intended as a helper and refresher for reviewers.
>=20
> Validating a release candidate
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> These guidelines are NOT complete.
>=20
> Requirements: Git, Java, and Maven.
>=20
> You can validate a release from a release candidate (RC) tag as =
follows.
>=20
> 1a) Download and decompress the source archive from:
>=20
> https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.0-RC1/source
>=20
> 1b) Check out the RC tag from git (optional)
>=20
> This is optional,  as a reviewer must at least check source =
distributions.
>=20
> git clone https://gitbox.apache.org/repos/asf/commons-jexl.git
> --branch commons-jexl-3.7.0-RC1 commons-jexl-3.7.0-RC1
> cd commons-jexl-3.7.0-RC1
>=20
> 2) Checking the build
>=20
> All components should include a default Maven goal, such that you can
> run 'mvn' from the command line by itself.
>=20
> 2) Check Apache licenses
>=20
> 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:
>=20
> mvn apache-rat:check
>=20
> 3) Check binary compatibility
>=20
> 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:
>=20
> mvn verify -DskipTests -P japicmp japicmp:cmp
>=20
> 4) Build the package
>=20
> This check should be included in the default Maven build, but you can
> check it with:
>=20
> mvn -V clean package
>=20
> 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
>=20
> 4b) Check reproducibility
>=20
> To check that a build is reproducible, run:
>=20
> mvn clean verify artifact:compare -DskipTests
> =
-Dreference.repo=3Dhttps://repository.apache.org/content/repositories/stag=
ing/
> '-Dbuildinfo.ignore=3D*/*.spdx.json'
>=20
> Note that this excludes SPDX files from the check.
>=20
> 5) Build the site for a single module project
>=20
> Note: Some plugins require the components to be installed instead of =
packaged.
>=20
> mvn site
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
>=20
> -the end-
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>=20