Hi Henri,
It looks like a problem remains.
Gary
On Sat, Jun 7, 2025, 04:14 GitBox wrote:
>
> The GitHub Actions job "Java CI" on commons-jexl.git/JEXL-440 has failed.
> Run started by GitHub user henrib (triggered by henrib).
>
> Head commit for run:
> 5a32d06d94f8
The Apache Commons team is pleased to announce Apache Commons JEXL
Version 3.5.0.
JEXL is a library intended to facilitate the implementation of dynamic
and scripting features in
applications and frameworks written in Java.
JEXL implements an Expression Language based on some extensions to the
This VOTE passes with the following binding +1 votes:
- Henri Biestro (henrib)
- Piotr P. Karwasz (ppkarwasz)
- Gary Gregory (ggregory)
TY all,
Gary
On Sat, Apr 12, 2025 at 1:59 PM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> JEXL
My +1
Gary
On Sat, Apr 12, 2025 at 1:59 PM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> JEXL 3.4.0 was released, so I would like to release Apache Commons
> JEXL 3.5.0.
>
> Apache Commons JEXL 3.5.0 RC2 is available for review
Hi Gary,
On 12.04.2025 19:59, Gary Gregory wrote:
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...
+1, release t
[+1]
Build & test ok; site - javadoc, reports, changes, release notes - look good.
Buit with:
mvn clean install site -s "$HOME/.m2/commons-settings.xml"
On:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/hbiestro/Java/apache-maven-3.8.6
Java version: 1.8.0_432,
We have fixed a few bugs and added enhancements since Apache Commons
JEXL 3.4.0 was released, so I would like to release Apache Commons
JEXL 3.5.0.
Apache Commons JEXL 3.5.0 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.5.0-RC2 (svn
revision 76223
Ack cancel RC1.
Henrib
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
RC1 is cancelled to account for issues found by Henri B.
Gary
On Fri, Apr 11, 2025 at 6:44 PM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> JEXL 3.4.0 was released, so I would like to release Apache Commons
> JEXL 3.5.0.
>
> A
We have fixed a few bugs and added enhancements since Apache Commons
JEXL 3.4.0 was released, so I would like to release Apache Commons
JEXL 3.5.0.
Apache Commons JEXL 3.5.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.5.0-RC1 (svn
revision 76215
7d29ff5b22dbc98deb52367472e5 / Henri Biestro <
> hbies...@cloudera.com>
> JEXL: JexlSandbox clean up;
> - added test related to a StackOverflow question (testSortArray);
>
> Report URL:
> https://github.com/apache/commons-jexl/actions/runs/10488198464
>
> With regards,
> GitHub Actions via GitBox
>
>
TY sebb!
Gary
On Wed, Jun 5, 2024 at 8:36 PM sebb wrote:
>
> On Thu, 6 Jun 2024 at 01:23, Gary Gregory wrote:
> >
> > The Apache Commons team is pleased to announce Apache Commons JEXL 3.4.0.
> >
> > Apache Commons JEXL is a library that facilitates the implementa
On Thu, 6 Jun 2024 at 01:23, Gary Gregory wrote:
>
> The Apache Commons team is pleased to announce Apache Commons JEXL 3.4.0.
>
> Apache Commons JEXL is a library that facilitates the implementation
> of scripting features in applications and frameworks written in Java.
>
&g
The Apache Commons team is pleased to announce Apache Commons JEXL 3.4.0.
Apache Commons JEXL is a library that facilitates the implementation
of scripting features in applications and frameworks written in Java.
Java 8 is required.
Historical list of changes:
https://commons.apache.org/proper
;
> > +1
> >
> > > On Jun 2, 2024, at 10:10 AM, Gary Gregory wrote:
> > >
> > > We have fixed a few bugs and added enhancements since Apache Commons
> > > JEXL 3.3 was released, so I would like to release Apache Commons JEXL
> > >
My +1
Gary
On Sun, Jun 2, 2024 at 11:20 AM Rob Tompkins wrote:
>
> +1
>
> > On Jun 2, 2024, at 10:10 AM, Gary Gregory wrote:
> >
> > We have fixed a few bugs and added enhancements since Apache Commons
> > JEXL 3.3 was released, so I would like to rele
+1
> On Jun 2, 2024, at 10:10 AM, Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> JEXL 3.3 was released, so I would like to release Apache Commons JEXL
> 3.4.0.
>
> Apache Commons JEXL 3.4.0 RC1 is available for re
: "mac os x", version: "14.5", arch: "aarch64", family: "mac"
hbiestro@D3CC9YTYXF-Henri-Biestro commons-jexl-3.4.0-RC1 %
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.or
We have fixed a few bugs and added enhancements since Apache Commons
JEXL 3.3 was released, so I would like to release Apache Commons JEXL
3.4.0.
Apache Commons JEXL 3.4.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.4.0-RC1 (svn
revision 69500)
The
27;re worried.
Cheers
Henrib
On 2024/01/23 10:40:20 Gary Gregory wrote:
> Please see below and fix ;-)
>
> Gary
>
> -- Forwarded message -
> From: GitBox
> Date: Tue, Jan 23, 2024, 5:37 AM
> Subject: [GH] (commons-jexl): Workflow run "Java CI" failed!
&
Please see below and fix ;-)
Gary
-- Forwarded message -
From: GitBox
Date: Tue, Jan 23, 2024, 5:37 AM
Subject: [GH] (commons-jexl): Workflow run "Java CI" failed!
To:
The GitHub Actions job "Java CI" on commons-jexl.git has failed.
Run started b
14be386795a66578119f13a / Henri Biestro
>
> JEXL-414: fixing wrong import order;
>
> Report URL: https://github.com/apache/commons-jexl/actions/runs/6911881308
>
> With regards,
> GitHub Actions via GitBox
>
---
yu Wu wrote:
>
> Some bug fixes and features (tailing comma etc.) would be very helpful for
> our usage.
> I have saw that the jexl 3.3.1 release note in source code, when can I get
> the JEXL 3.3.1 version in maven repostory?
Some bug fixes and features (tailing comma etc.) would be very helpful for our
usage.
I have saw that the jexl 3.3.1 release note in source code, when can I get the
JEXL 3.3.1 version in maven repostory?
Best,
Xiangyu
Good to know, thanks for pointing this out.
Reduced flags public exposure in JEXL per last commit.
Henrib
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
the html files, but it would be useful to
know if there is a bug in the documentation or the release plugin (or
both).
> Sebb
> [1] https://lists.apache.org/thread/oowy3bq41zncsdbns4yxslknr8r2dmbn
> [2] https://dist.apache.org/rep
There's another reason why using public constants is problematic:
The Java compiler inlines constants into the class that uses them.
So, if we change a constant and only recompile that class and not the
referencing class, we can get inconsistent constant values.
This means that changes to public
A recent change to JexlFeatures made some flag combinations public.
Seems to me that this unnecessarily exposes the internal
representation, which makes it much harder to change it later.
Making constants public can constrain future changes, whereas
providing access via methods is easier to mainta
Your are correct, the engine (and the parser) do use its own JexlFeatures
copies (expressionFeatures/scriptFeatures members) that are never modified
after creation. An equivalent rule applies for JexlOptions btw, copied for
isolation for each evaluation. Those classes, by themselves, even if t
On Fri, 20 Oct 2023 at 19:09, Henri Biestro wrote:
>
>
> JexlPermissions concrete classes are but since this is an interface, anyone
> could create a non-thread safe instance and use it. The same way a
> JexlFeatures could be corrupted by being constructed with a non-thread safe
> namespace pre
JexlPermissions concrete classes are but since this is an interface, anyone
could create a non-thread safe instance and use it. The same way a JexlFeatures
could be corrupted by being constructed with a non-thread safe namespace
predicate (making side-effects etc).
And for JexlFeatures, using
In general, I assume nothing is thread-safe unless documented as such.
Gary
On Fri, Oct 20, 2023, 12:27 PM sebb wrote:
> Are instances of the classes JexlFeatures and JexlPermissions intended
> to be thread-safe?
>
> I have seen mention that they can be shared between threads.
>
> However Jexl
Are instances of the classes JexlFeatures and JexlPermissions intended
to be thread-safe?
I have seen mention that they can be shared between threads.
However JexlFeatures is does not appear to be thread-safe (has mutable
fields which are not safely published). Not looked at JexlPermissions
in de
not work, as I thought most of it was now automated?
AFAICT the rest of the commit was OK.
Sebb
[1] https://lists.apache.org/thread/oowy3bq41zncsdbns4yxslknr8r2dmbn
[2] https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC2/binaries
Thanks, Henri, for a quick reply. Really appreciate it.
-
Aditya Kumar1
Technology Architect
Precisely.com
-Original Message-
From: Henri Biestro
Sent: Monday, August 7, 2023 5:09 PM
To: dev@commons.apache.org
Subject: Re: [JEXL] Detecting infinite loops in JEXL Scripts
This message
for
too long. (see ScriptCallableTest#testFuture).
Cheers
On 2023/08/07 10:59:58 Aditya Kumar1 wrote:
> Hi,
>
> I am planning to use JEXL library in my SaaS based product to run
> JavaScripts/JexlScripts(I understand, Jexl is not exactly java script).
>
> Since, security
ea. (As in: how do I integrate my own classes/packages?
-or- how do I ensure scripts are readonly and don't modify data?).
On 2023/08/07 10:08:59 Gary Gregory wrote:
> Do we need better documentation on the site?
>
> Gary
>
> On Mon, Aug 7, 2023, 5:45 AM Henri Biestro wrote
Hi,
I am planning to use JEXL library in my SaaS based product to run
JavaScripts/JexlScripts(I understand, Jexl is not exactly java script).
Since, security is one of the most important requirements for any SaaS based
product, I am going to use Jexl Sandbox and Jexl Features to secure my
PM
To: dev@commons.apache.org
Subject: Re: Exposing my own/wrapper functions using JEXL
This message originated Externally. Use proper judgement and caution with
attachments, links, or responses.
Hi;
JEXL 3.3. has increased default security by restricting permissions to a very
narrow set of al
Do we need better documentation on the site?
Gary
On Mon, Aug 7, 2023, 5:45 AM Henri Biestro wrote:
> Hi;
> JEXL 3.3. has increased default security by restricting permissions to a
> very narrow set of allowed classes. In your case, you need to allow JEXL to
> introspect you
Hi;
JEXL 3.3. has increased default security by restricting permissions to a very
narrow set of allowed classes. In your case, you need to allow JEXL to
introspect your package by configuring your permissions. Have a look at
JexlPermissions javadoc for more explanations.
On JEXL 3.3, with Java
Hi,
I was trying to expose my own functions using JEXL library. I am trying the
below example.
public static class MyMath {
public double cos(final double x) {
return Math.cos(x);
}
}
public static void testCustomFunction2() {
try
Hi Henri,
Very well :D
I've created and issue at https://issues.apache.org/jira/browse/JEXL-396 and a
PR is ready for review.
Cheers,
Andres
On 2023/04/28 12:51:29 Henri Biestro wrote:
> Hello Andres;
> Interesting idea. A PR using Moditect conditioned on jdk profile (so we can
Hello Andres;
Interesting idea. A PR using Moditect conditioned on jdk profile (so we can
continue targeting java 8 without module info?) could be a first step to gauge
feasibility.
Cheers,
Henrib
-
To unsubscribe, e-mail: dev-u
ards,
> Gilles
Well, that's my end goal to be precise ;-)
Right now I'm in need for full Java modules for the following Commons
components: codec, compress, io, jexl, lang3, net, text. But certainly other
developers may want to have similar capabilities on other Commons components
Hi.
Le mar. 25 avr. 2023 à 17:37, Andres Almiray a écrit :
>
> Hello!
>
> I'd like to gauge interest in adding a full Java module descriptor (a.k.a
> JPMS though the use of the acronym is discouraged) to commons-jexl.
It's an interesting functionality, but I think th
Hello!
I'd like to gauge interest in adding a full Java module descriptor (a.k.a JPMS
though the use of the acronym is discouraged) to commons-jexl.
The codebase is currently Java 8 compatible. Adding a full Java descriptor
requires using Java 9+ in the build but does not force the
Done. :-)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Thanks Henri! Don't forget to update changes.xml please.
Gary
On Tue, Apr 11, 2023, 12:19 Henri Biestro wrote:
> Merged it.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail:
Merged it.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Hi;
Default permissions have changed with JEXL 3.3 to help with application
security.
I created the PR that restores the tests (
https://github.com/apache/commons-scxml/pull/123 ).
Henri
-
To unsubscribe, e-mail: dev-unsubscr
commons.scxml2.model.CustomActionTest
Error:
org.apache.commons.scxml2.model.CustomActionTest.testCustomActionEventPayloadHelloWorldJexl
Time elapsed: 0.034 s <<< FAILURE!
org.opentest4j.AssertionFailedError: Invalid intermediate state ==>
expected: but was:
Maybe someone else that knows more about scx
Hi All
Did we create a bug in the recently released 3.3 which surfaces as
https://github.com/apache/commons-scxml/pull/121 ?
Gary
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev
The Apache Commons JEXL team is happy to announce the release of version
3.3.
JEXL is a library intended to facilitate the implementation of dynamic and
scripting features in applications and frameworks written in Java.
This is a feature and bug-fix release.
Site: https://commons.apache.org
This VOTE passes with the following binding +1 votes:
- Bruno Kinoshita
- Gary Gregory
- Henri Biestro
i, Mar 17, 2023 at 2:28 PM Henri Biestro (Apache)
wrote:
>
> 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
Thanks Bruno :-)
JEXL still needs another vote.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
"5.15.0-67-generic", arch: "amd64", family:
"unix"
Cheers
Bruno
On Fri, 17 Mar 2023 at 19:28, Henri Biestro (Apache)
wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons JEXL 3.2.1 was released, so I w
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
Would you very briefly outline the bug FTR?
TY!
Gary
On Thu, Mar 16, 2023, 15:46 Henri Biestro wrote:
>
> Unfortunately, more testing revealed a regression and a bug.
> RC1 fails, RC2 will be proposed momentarily.
>
> -
> To un
Late tests reopened JEXL-393 and discovered a regression (JEXL-394).
RC2 will be proposed momentarily.
Sorry.
Unfortunately, more testing revealed a regression and a bug.
RC1 fails, RC2 will be proposed momentarily.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
o read POM
org.codehaus.plexus.util.xml.pull.XmlPullParserException: UTF-8 BOM
plus xml decl of ISO-8859-1 is incompatible (position: START_DOCUMENT
seen wrote:
>
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons JEXL 3.2.1 was released, so I wo
;, version: "5.15.0-67-generic", arch: "amd64", family:
"unix"
Site reports look good too.
Thanks!
On Mon, 13 Mar 2023 at 18:01, Henri Biestro (Apache)
wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons JEXL
Noted, sorry for the broken Clirr report link.
Clirr has been replaced by Japicmp in JEXL.
Henri
On 2023/03/13 17:15:43 Gary Gregory wrote:
> Henri,
>
> The starred items in the template are meant to be edited by the RM. For
> example, you provide a link to a non-existent CLIRR repor
Apache Commons JEXL 3.2.1 was released, so I would like to release
> Apache Commons JEXL 3.3.
>
> Apache Commons JEXL 3.3 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC1 (svn
> revision 60566)
>
> The Git tag commons-jexl-3.
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 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.3-RC1 (svn
Dear all;
I intend on starting the release of JEXL 3.3 with a landing (ideally) in
early March..
If you've any feedback on features, bugs, etc, that may impact that
release, please reach out now.
Cheers
> You have to consider the software in the context it is intended to be
> used.
Thank you for clarifying and illustrating those notions. We are in agreement
about JEXL intended usage and where the responsibility lies wrt security
choices.
But even in its usage context, with authent
ually entails. Let's assume we want those users to enter a (JEXL)
expression to express their functional need (think of an enterprise spreadsheet
of some kind with some built-in constraints). Is this considered an 'unsafe
input' by essence ? If so, we need to 'sanitise
Let's restrict this discussion to the case of 'authenticated and authorised
users' of an 'enterprise platform'.
When we talk about 'unsafe input' vs 'safe input', I'm still confused about
what this actually entails. Let's assume we want tho
On 26/10/2022 08:58, Henri Biestro wrote:
Fair points, thank you. They seem to lead into the point of view that JEXL (or
any scripting solution?) should not expose any feature that could be considered
security-related avoiding the CVE potential turmoils alltogether. Trusted
sanitised input is
Fair points, thank you. They seem to lead into the point of view that JEXL (or
any scripting solution?) should not expose any feature that could be considered
security-related avoiding the CVE potential turmoils alltogether. Trusted
sanitised input is expected and required so this is a moot
On 24/10/2022 17:02, Henri Biestro (Apache) wrote:
Hello Commons;
JEXL-381 is an attempt at making JEXL's default more secure or at least
less 'permeable' wrt to the application/platform/JVM/file-system/host that
runs it. Based on JexlPermissions - a crude security visibility
Hello Commons;
JEXL-381 is an attempt at making JEXL's default more secure or at least
less 'permeable' wrt to the application/platform/JVM/file-system/host that
runs it. Based on JexlPermissions - a crude security visibility manager -,
this restricts the *default* behavior of wha
exl.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
> new f909826e JEXL: Attempt to bump checkstyle from 9.3 to 10.3, add
> plugin profile for jdk8
> new 22d92e50 Merge remote-tracking branch 'origin/master&#
The following people voted on release Apache Commons JEXL 3.2.1:
Rob Tompkins +1
Bruno P. Kinoshita +1
Gary Gregory +1
Henri Biestro +1
Thanks!
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional
+1
All of these should be addressed post-release:
The release notes header says 3.2, not 3.2.1 here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2.1-RC1/RELEASE-NOTES.txt
We've never talked about "micro" releases, this should be labeled a
"mainten
japicmp, will do.
Thanks
On 2021/06/23 23:05:27, Rob Tompkins wrote:
> +1 builds and tests with 8 and 11
>
> signatures good
>
> reports all look reasonable
>
> (nit -> can we get japicmp implemented here?)
>
-
To unsubs
critical bugs besides releasing a 'service
> pack' version ?
>
> My hopeful +1
> Cheers
>
> On 2021/06/18 10:48:37, Henri Biestro wrote:
>>
>> We have fixed 2 critical bugs and 1 enhancement since Apache Commons JEXL
>> 3.2 was released, so I would lik
one has
>> anything to object, just because no-one had the time to look at it. Do we
>> have any (other) way to react to critical bugs besides releasing a 'service
>> pack' version ?
>>
>> My hopeful +1
>> Cheers
>>
>> On 2021/06/18 10:4
'service
> pack' version ?
>
> My hopeful +1
> Cheers
>
> On 2021/06/18 10:48:37, Henri Biestro wrote:
> >
> > We have fixed 2 critical bugs and 1 enhancement since Apache Commons
> JEXL 3.2 was released, so I would like to release Apache Commons JEXL 3.2.1.
es, and Maven repo. Found no issues. Also
manually inspected a couple files from the dist area, everything looking good.
Thanks for RM'ing Henri!
Bruno
On Friday, 18 June 2021, 10:48:40 pm NZST, Henri Biestro
wrote:
We have fixed 2 critical bugs and 1 enhancement since Apache Com
time to look at it. Do we have any
(other) way to react to critical bugs besides releasing a 'service pack'
version ?
My hopeful +1
Cheers
On 2021/06/18 10:48:37, Henri Biestro wrote:
>
> We have fixed 2 critical bugs and 1 enhancement since Apache Commons JEXL 3.2
> was r
We have fixed 2 critical bugs and 1 enhancement since Apache Commons JEXL 3.2
was released, so I would like to release Apache Commons JEXL 3.2.1.
Apache Commons JEXL 3.2.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jexl/3.2.1-RC1 (svn revision
48410
You only publish the JEXL site, not the whole Commons site.
Gary
On Mon, Jun 7, 2021, 15:54 Henri Biestro wrote:
>
> I've been fumbling a bit with the release process, especially the site
> part, I'm pretty sure I've missed a (few) steps somewhere since the site
>
hole commons site or
only the JEXL site ? The procedure
described in http://commons.apache.org/site-publish.html is very confusing to
me now... And the 'being in flux' warning or the yaml publishing mail make me
even more confused.
A quick look at the site, a little bit of guidanc
The following people voted on release JEXL 3.2:
Gary +1
Matt +1
Henrib +1
Gary, Matt, thank you!
On 2021/06/03 18:34:40, Henri Biestro wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons JEXL 3.1 was released, so I would like t
:
> /Library/Java/JavaVirtualMachines/adoptopenjdk-16.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
>
> Gary
>
> On Thu, Jun 3, 2021
os x", version: "11.4", arch: "x86_64", family: "mac"
Gary
On Thu, Jun 3, 2021 at 2:34 PM Henri Biestro wrote:
>
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons JEXL 3.1 was released, so I would lik
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
enerate the javadoc whilst 'release' plugin uses the build section to do
> the same. Fixed the issue by adding the same javadoc plugin configuration
> in build section of the pom.xml.
>
> On 2021/01/05 17:05:32, Henri Biestro wrote:
> > Hello Team; Happy new year!
> &g
05:32, Henri Biestro wrote:
> Hello Team; Happy new year!
>
> I'm trying (again) to release JEXL 3.2 and I'm stuck at the 'Maven release
> plugin' step in https://commons.apache.org/releases/prepare.html.
>
> Despite the fact a 'maven site' from Intell
d when writing code, validating code and also compiling code.
> 3 i think is also used when running unit tests
>
> Not sure if that will show other issues of fix this issue, hopefully
> it maybe highlight if different jvm's are being used when comparing
> inside and outside intel
none
..
I seek help, not diss.
On 2021/01/05 19:00:57, Gary Gregory wrote:
> You "should" fix the Javadoc warnings; -) or disable doclint.
>
> Gary
>
>
> On Tue, Jan 5, 2021, 12:06 Henri Biestro wrote:
>
> > Hello Te
f fix this issue, hopefully
> it maybe highlight if different jvm's are being used when comparing
> inside and outside intellij.
>
> John
>
>
> On Tue, 5 Jan 2021 at 17:06, Henri Biestro wrote:
> >
> > Hello Team; Happy new year!
> >
> > I'
other issues of fix this issue, hopefully
it maybe highlight if different jvm's are being used when comparing
inside and outside intellij.
John
On Tue, 5 Jan 2021 at 17:06, Henri Biestro wrote:
>
> Hello Team; Happy new year!
>
> I'm trying (again) to release JEXL 3.2 and I&#
You "should" fix the Javadoc warnings; -) or disable doclint.
Gary
On Tue, Jan 5, 2021, 12:06 Henri Biestro wrote:
> Hello Team; Happy new year!
>
> I'm trying (again) to release JEXL 3.2 and I'm stuck at the 'Maven release
> plugin' step in https:
Hello Team; Happy new year!
I'm trying (again) to release JEXL 3.2 and I'm stuck at the 'Maven release
plugin' step in https://commons.apache.org/releases/prepare.html.
Despite the fact a 'maven site' from IntelliJ does succeed, a 'mv
release:prepare -DtryRun
parent POM now defines much more, so the JEXL POM now only needs
to define the excludes.
S.
On Tue, 3 Nov 2020 at 19:20, Henri Biestro wrote:
>
>
> I still don't get why I need to (re)configure so many plugins in JEXL's pom
> - any explanation is still welcome - but I managed t
1 - 100 of 796 matches
Mail list logo
