commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henrib <hen...@apache.org>
Subject Re: [JEXL] binary compatibility
Date Mon, 28 Nov 2011 15:55:12 GMT
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.

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...

Any hint/advice/idea ?
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: http://apache-commons.680414.n4.nabble.com/JEXL-binary-compatibility-tp4114818p4115683.html
Sent from the Commons - Dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message