commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [JEXL] binary compatibility
Date Mon, 28 Nov 2011 16:26:51 GMT
On 28 November 2011 15:55, henrib <> wrote:
> I added @since 2.1, renamed the Uberspect.getConstructor, removed final for
> silent & strict in Interpreter (although Interpreter instances probably
> never need to change those at runtime) but there are still 21 clirr errors
> that I'm afraid many will consider as show-stoppers for release.

Not if they can be shown to be unused by end-users.

> I'm pretty sure that no active JEXL user would really be bothered by the 2.1
> API modifications - and even less so by the binary incompatibility - but I
> don't see how the case can be made...

JMeter uses Jexl2 - don't have time to try it now, but I will try
tomorrow and see if it is affected by the API breaks.

> Any hint/advice/idea ?

There are still a few errors that could be fixed.
e.g. the visit() changes - would it work to re-introduce dummy
deprecated classes ASTFloatLiteral and ASTIntegerLiteral?
Or define them in terms of the new classes?

JexlArithmetic.strict can be made non-final
Likewise the method changes in UnifiedJEXL$Expression could be
reverted (and pending changes flagged).

I think it's now quite close, apart from the Script interface, which
may be allowed.

> I've got a migrated-to jexl3 code base ready just in case jexl2 is a
> dead-end.
> Cheers,
> Henrib
> --
> View this message in context:
> Sent from the Commons - Dev mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message