We have fixed a few bugs and added enhancements since the release of
Apache Commons JEXL 3.7.0, so I would like to release Apache Commons
JEXL 3.7.1.

Apache Commons JEXL 3.7.1 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.1-RC1 (svn
revision 88587)

The Git tag commons-jexl-3.7.1-RC1 commit for this RC is
9a03752243dcf81ea9e2bebdcdb59e18eb2b43bc, which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-jexl.git;a=commit;h=9a03752243dcf81ea9e2bebdcdb59e18eb2b43bc
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-jexl.git
--branch commons-jexl-3.7.1-RC1 commons-jexl-3.7.1-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1970/org/apache/commons/commons-jexl3/3.7.1/

These are the artifacts and their hashes:

#Release SHA-512s
#Thu Oct 15 20:24:33 UTC 2026
commons-jexl-3.7.1-bin.tar.gz=cd5c10eaea9e0a7454bb998e81924b119e37362dd7a37caaf847c528e1a12d62d2ec9aaeb9e4d752e9f35d44ed9df7df7f9e61f2b7ca077296238e4be7843b03
commons-jexl-3.7.1-bin.zip=bea2269a2676685845e24d7c174077cab8f8d8d2ec3c4a5911c4d048603a66eaa5bb1b3fcf44973fb6ee0c0434c931cba7ce5981ca63f59d4f9729e241bd9030
commons-jexl-3.7.1-src.tar.gz=e1eee7377bb148c2e684d8fa216707ddd75aaf538ff790619f92bcdf180832184391355fa37975d9de1ae21fdad0d55c8fa7e2597d3c933774e467297500bf6a
commons-jexl-3.7.1-src.zip=ec66eef56c2b62bf39b5d857228ae40162ddd1ab32ebc58cb9f4fc2be2225f3fec8678730b24959db076e187817a4c32384f0ecf4c2d58497904a187f756fd10
commons-jexl3-3.7.1-bom.json=2f1974e494ea3d047bfdfd5ee943bde1e8b43c9958c6245333685116a56fc95bb025081e0fcef3ba909f5bcbef6e51b56a3fbdbf78793fb93f67384bccda0809
commons-jexl3-3.7.1-bom.xml=02696a95895d624c54fa2fc03e455a332eacc5ec9d4c1d3810ff290bef946651f2350506f125a6a4ac5e082838bfc1b73854ae4ad06d0b90a720a6a2a80dd70d
commons-jexl3-3.7.1-javadoc.jar=cf973c1ec51da03ec8f7fc22a6b39c35d213be33e23e6ebab42306aae6f4904db68217de8fa81444963c83cda98cbe71089379f2289d3b2e4271b3317ee36a5b
commons-jexl3-3.7.1-sources.jar=12e02eb65f0715c703fe399fbf57473c89c2c45cf33750dc5cb694735e9a258d40111577557bf610e64dad84f61a355968eabbf5757afda00a0d51f427343303
commons-jexl3-3.7.1-test-sources.jar=d029c41dfac7dfbc082a923241034b6fc615073d788d599100193195cdd97b84b26c82ad43ab2ad83a24a16e27a748e500907e966c268155b19018fdf11dbd8d
commons-jexl3-3.7.1-tests.jar=1a54c1bbd6fb7587ed1c941c47892681048956d4f3875e7070015f73b22928dfce348fdc6ce38e624205b97f03312fbe326ead7b1959398084c8c43d0c832780
org.apache.commons_commons-jexl3-3.7.1.spdx.json=d239ebac2677f3b3557ce754a06a0a9b6db3bfccc253bae1068830463f58c874d254471cadad26dc8704b048be57a0dcdd0079554f43a24b87de11aac3ea9f94


I have tested this with 'mvn' and 'mvn clean install site' using:

openjdk version "25.0.4.1" 2026-08-18
OpenJDK Runtime Environment Homebrew (build 25.0.4.1)
OpenJDK 64-Bit Server VM Homebrew (build 25.0.4.1, mixed mode, sharing)

Apache Maven 3.10.0 (c43a36b8d67be7e0805a411bc0898af1a51f5472)
Maven home: /opt/homebrew/Cellar/maven/3.10.0/libexec
Java version: 25.0.4.1, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@25/25.0.4.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8, time zone: UTC
OS name: "mac os x", version: "26.7.1", arch: "aarch64", family: "mac"

Darwin ****.local 25.6.0 Darwin Kernel Version 25.6.0: Tue Aug 18
17:48:46 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6041
arm64

Docker version 29.8.2, build 7fc2dff


Details of changes since 3.7.0 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.1-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.1-RC1/site/changes.html

Site:
    
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.1-RC1/site/index.html
    (Note some *relative* links are broken and the 3.7.1 directories
are not yet created - these will be OK once the site is deployed.)

*** JApiCmp Report (compared to 3.7.0):
    
https://dist.apache.org/repos/dist/dev/commons/jexl/3.7.1-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/jexl/3.7.1-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.7.1-RC1/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.7.1-RC1 commons-jexl-3.7.1-RC1
cd commons-jexl-3.7.1-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]

Reply via email to