On 22/11/2009, henrib <[email protected]> wrote:
>
> Any other opinion ?
> Sebb, Rahul, what's your take ?
I've not used the JEXL API at all, except via BSF/JSR-223 (which have
unchanged APIs).
So I can't really comment on whether the JEXL API changes are likely
to cause problems or not.
Seems to me it would be slightly safer to rename the packages, but I
won't veto keeping the same names.
> Thanks
> Henrib
>
>
>
> Henrib-2 wrote:
> >
> > One (non Maven related) question for the JEXL community:
> >
> > The (soon-to-be published) JEXL-2.0 RCx version comes with a lot of
> > changes. The upper level API deprecates ExpressionFactory & ScriptFactory
> > - replaced by JexlEngine -, Expression methods that used to throw
> > exceptions (ParseException, Exception) throw unchecked exceptions and the
> > inner level classes (o.a.c.{util,introspection,etc}) have to many changes
> > to be listed.
> >
> > Upper level API code compatibility has been checked through Jelly and more
> > recently through Commons Configuration; 1.1 behavior seems preserved
>
> > enough for the switch to JEXL-2.0 to be one compilation away.
>
> > However, with so many changes and not so many checks, it may be preferable
> > to be on the safe side and put the whole JEXL-2.0 into
> > org.apache.commons.jexl2; this would allow 1.1 dependant code to continue
> > living its merry way (OSGi non withstanding) and let switchers decide when
> > to actually perform the switch.
> >
> > We need your opinions and options; let us know.
> > Cheers
> > Henrib
> >
> >
>
> --
>
> View this message in context:
> http://n4.nabble.com/JEXL-2-0-o-a-c-jexl-or-o-a-c-jexl2-tp727081p758756.html
>
> Sent from the Commons - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
