One might argue that JEXL does not have that many users so jar hell is very (very) unlikely - no Apache project depends on jexl2 afaik - and that forcing "up to date/snapshot" users to switch to a new package when they're already used to recompile against the latest JEXL version is adding burden on their side (i.e. replace all o.a.c.jexl2 imports with o.a.c.jexl3, update maven dependencies, etc.) with no practical benefit.
However, following the commons best practice being the wisest route to release, I'll re-attempt an RC after migration to o.a.c.jexl3. Regards, Henrib -- View this message in context: http://apache-commons.680414.n4.nabble.com/CANCELLED-VOTE-Release-JEXL-2-1-based-on-RC1-tp4114443p4115226.html Sent from the Commons - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
