We have fixed quite a few bugs and added some significant enhancements since
Apache Commons JEXL 3.1 was released, so I would like to release Apache Commons
JEXL 3.2.
Apache Commons JEXL 3.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1 (svn revision
48128)
The Git tag commons-jexl-3.2-RC1 commit for this RC is
3bbdc91d649a085564561a6e93ba9e052d841508 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-jexl.git;a=commit;h=3bbdc91d649a085564561a6e93ba9e052d841508
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jexl.git --branch
commons-jexl-3.2-RC1 commons-jexl-3.2-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1550/org/apache/commons/commons-jexl3/3.2/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Jun 03 20:13:49 CEST 2021
commons-jexl-3.2-bin.tar.gz=65593259dcb4e4cb3621766a59206e579d487ca0d56010ac8c514c21df2f0e5c90b05cb36b2c65f8e191b4fb86e91a5124e546d7017927efdcd3cbffeb8e33fa
commons-jexl-3.2-bin.tar.gz.asc=56ffe095ec050cb3047b9a9463319427d1799351dc16526e4b066cbfbe3d0554ff38fa970e3eac36fe4f96d93f6918dee38a3aeaefbbaafca62dc258c208755f
commons-jexl-3.2-bin.zip=184dfaa4e9e6aaca1e421a9c220f3c13902a71454a6d35eea8347017b93944a5c2f9455722b49a496e7e616481aa9bfba24ce5a4bb8cfc0b6f8f39680ddec95f
commons-jexl-3.2-bin.zip.asc=56e5a673a59b422f994281e7e30e74945cee3576b4953077d8c25de9483bd3b24f51f16d5e18b51e74ae649853567b5f0a9900cb61a81aa3b47bd01e22771874
commons-jexl-3.2-src.tar.gz=cd489cc0f6c117a24be4aedaf1e5a8cf06183085d307c9b855d62f7302709979e4482d6de8da87535381adae8d4671c5cea2af3bb3818050613db87da12aba5f
commons-jexl-3.2-src.tar.gz.asc=af323b1bac610aea3166cf80433e27aa9c0d7396b56903329ef1d6faa0f808268da729e71c72c69be9695e077c3467abdc2f4d1d8e8a7c9cf53311829ae8e766
commons-jexl-3.2-src.zip=f10e0a83c6d98f2f12cacfd92acb2b326f718052a73c539c8ca7f39cc60aad4b48331d5ad644dc9c4367ab5d8b1280bf44ccacee6b29fb138f1c12f0f2e285be
commons-jexl-3.2-src.zip.asc=d99a223f3f5c813316d1ca112a1ee21af84c78475925415d8277b3ecdedd97e3b29a17ba5db5f65f22d945a541f38651f4bb1025892633a4f8cd4988e6d37815
commons-jexl3-3.2-javadoc.jar=476200ebabb311e3a2197555b19f99ad284cca3501fa170fefd4885c5c310d162340a395dc7ebca842a0483700ca0d689ce42f19557efeab734b4315efa95791
commons-jexl3-3.2-javadoc.jar.asc=816934c204b16946b9e8482d7fc2784d0f0a845ff4345509265db0f86a6a335fcfcc5c861a78fc431a71122fafc3a5720cb8edabaa35029cc34e4a49faf55135
commons-jexl3-3.2-sources.jar=4cce369e319d8b83c835124f1c242a4e6502945d28cc8df7bcd36c09cade6aa13d5072b4407ddb01976a13a50df3ec8749e5896df076a501a6fc35eb29a8a8fd
commons-jexl3-3.2-sources.jar.asc=1eabb310ddcfef0d3caf4d645361549390b22a9be46591ba2c77974e178aa1992e5d88b27cb8145b4437e5bb772577f1a7c6f311cf0aac3129f6ea74574f1a37
commons-jexl3-3.2-test-sources.jar=944469e6ee58df60807305a4c1386239656efa3fa432a6ff23250e8f878e2135b0658e2e18a1959a1e1a1748764d9e7b6ef264404366d06ae7ab79b4db445be0
commons-jexl3-3.2-test-sources.jar.asc=725e071ce91dd8c6ce8b8761834bb7578f5c725083bf7614c4f41e72ff2b76be7a03181fa36ec90da534025be236c418294338969d93b64dc87fd7afce4d38e0
commons-jexl3-3.2-tests.jar=2c986cc9c3943f2d5231e77481819c78f37271e8586d3cc41d639664686de44519b7acb68f34f9dce1781fb70a2330bfff75dc3d3050463a403ee894260d6a98
commons-jexl3-3.2-tests.jar.asc=e36eb120d1b71689efa6200707f9e58436621e02cd97bff9ad88da323197f0cf9065ebb4c879179ac6f0aeead165eca224e905018eac71f1fe59e80c010e25c3
commons-jexl3-3.2.jar.asc=97522856c9a68cef53b421d44b350e7998803e459d54edaf20f07be8373968e2009f8734d7d6e89a35757993b227408e6701302a2d2483655fbdc93c2c698756
commons-jexl3-3.2.pom.asc=0cf4afe3be69f9a7a6e0755ef9a095c903b7979c9585fbe6ecff11808d36c3ccd11b06b3dffd00a0a1c332599613b5afcbef827462b0bbca2140a398cf6baf47
(no need for .asc hashes!)
I have tested this with 'mvn clean install site' using:
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T21:00:29+02:00)
Maven home: /Users/henri.biestro/Java/apache-maven-3.6.1
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre
Default locale: en_FR, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
Details of changes since 3.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/site/index.html
(note some *relative* links are broken and the 3.2 directories are not yet
created - these will be OK once the site is deployed.)
CLIRR Report (compared to 3.1):
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/site/clirr-report.html
JApiCmp Report (compared to 3.1):
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/site/japicmp.html
Note that Clirr reports 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.
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2-RC1/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 that 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.2-RC1 commons-jexl-3.2-RC1
cd commons-jexl-3.2-RC1
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
