We have fixed quite a few bugs and added some significant enhancements
since Apache Commons JEXL 3.2.1 was released, so I would like to release
Apache Commons JEXL 3.3.

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

Only changes since RC1 are 2 fixes for issues discovered during late
testing, one regression (JEXL-394) and one reopen (JEXL-393).

The Git tag commons-jexl-3.3-RC2 commit for this RC is
4e91dc63dba73204c8a69295e1ab402c1ab7d3e4 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jexl.git;a=commit;h=4e91dc63dba73204c8a69295e1ab402c1ab7d3e4
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-jexl.git --branch
commons-jexl-3.3-RC2 commons-jexl-3.3-RC2

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1627/org/apache/commons/commons-jexl3/3.3/

These are the artifacts and their hashes:

#Release SHA-512s
#Fri Mar 17 18:51:22 CET 2023
commons-jexl-3.3-bin.tar.gz=70d349cdb450637a7334b0d2943afa14d990104d6ae33215d965ea01c93847a21b13c5a8c5e779af6a58156d2d4bf6eff7fc8b651db35332417f01e1e2a9461b
commons-jexl-3.3-bin.zip=271d4b98955430e26b2b36eef1186801acfe4a6f0f2e7a8c6be214fc0d9b98733628e79a5de3351430f4d3ddb8ca41cca8d93db7320270ce7fc3a5ec69f72e58
commons-jexl-3.3-src.tar.gz=241a7d2e8e50a00e7ab64f718ffd8e4592326e5d4cb36434445c466450340adab4116bbe670e9d34f68d5895d4ceb997dd598cb5101d167824cb84a39449d82e
commons-jexl-3.3-src.zip=5ec8efbfcdba85ee449013365e1f655fa5cc9d28dcfa8033ae97a21626c984ae02a0953da2a9b29c472975e2120cab4a96601a75bb8dbc6748cf48b857bf0685
commons-jexl3-3.3-bom.json=c7387d4b5c37bcbcd07096c9cf288bf00bee688f439649721ad0b21efb841cdd0dc276999ac333a00ad3fd075088d3271e180a157995b70f7d2dc1f241b857ca
commons-jexl3-3.3-bom.xml=a5ebbe64f2c1f8751188c28299a8374ba3f7fc1e00ab764073e43ec5506d3e04be23e96d822c80cb463e848dbab7f0c67c6e068bb2ca9acfe4d00360e1c30eec
commons-jexl3-3.3-javadoc.jar=790f36988e7f8b0fa757623e15415023a800e7e60f205e342ad6caf2bb5a9d647adaec3069119ada4312821df739c7e0bf97b04a4b9dece7a7d882b9577cafdf
commons-jexl3-3.3-sources.jar=e3ce6e17933859d9545263fdc79e345e8805c6c853ab8852d60bbea3108116c3d9c88333b2f08f81bd463f5a02388a97bbcf1062bf7144b4efd78c4854efd492
commons-jexl3-3.3-test-sources.jar=6f80cad1854047708a05db397b2bbeaa5242d8342adb7a973dc285ffaa8cbca1ccfb1c6e986d40fd106bde5935af08d42b0c3b6d1cabdd1fee3592a5eddc2a58
commons-jexl3-3.3-tests.jar=d30288dc0143b81a0fa133b6e421e006e9f2faad351e57013f52401fc326933c0e1d88482a92f78e41fdb9a286d2c62d5d978e801bf5a131a636ef17bd7eb16b
org.apache.commons_commons-jexl3-3.3.spdx.json=07226f97af94fa6cee09fd28d4cbb34f51853984473866683fa21dd9a462b8522566634a2c082fe2c8ba6cd8aed8eb365a85912c251691bbb13687b3cf9546ed



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

Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /Users/henri.biestro/Java/apache-maven-3.8.1
Java version: 1.8.0_345, vendor: Azul Systems, Inc., runtime:
/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
Default locale: en_FR, platform encoding: UTF-8
OS name: "mac os x", version: "13.2.1", arch: "aarch64", family: "mac"

on

Darwin l-hbiestro.home 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30
20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 arm64

And with:

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /Users/henri/Java/apache-maven-3.9.0
Java version: 1.8.0_362, vendor: Azul Systems, Inc., runtime:
/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"

and

AApache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /Users/henri/Java/apache-maven-3.9.0
Java version: 17.0.6, vendor: Azul Systems, Inc., runtime:
/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"

on

Darwin hornet.home 19.6.0 Darwin Kernel Version 19.6.0: Tue Jun 21 21:18:39
PDT 2022; root:xnu-6153.141.66~1/RELEASE_X86_64 x86_64


Details of changes since 3.2.1 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC2/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC2/site/changes-report.html

Site:

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

JApiCmp Report (compared to 3.2.1):

https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC2/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC2/site/rat-report.html

KEYS:
  https://www.apache.org/dist/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,

Henri Biestro,
Release Manager (using key 4E066E0459CD109B)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate
==============================

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-jexl.git --branch
commons-jexl-3.3-RC2 commons-jexl-3.3-RC2
cd commons-jexl-3.3-RC2

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you
then must check.

mvn apache-rat:check

3) Check binary compatibility

Older components still use Apache Clirr:

This step is not required if the site includes a Clirr report page which
you then must check.

mvn clirr:check

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which
you then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

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

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

6) Build the site for a multi-module project

mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

Reply via email to