Rahul Akolkar wrote:
>
>
> And if by optionality of jexl-compat you meant not building it every
> time, we could use profile activation so the compat module only gets
> built if a -Pcompat switch is provided, for example.
>
> -Rahul
>
>
I'm still trying to find the best solution to ease the transition from jexl1
to jexl2.
Providing the 80% use-case compatibility would be nice but jar packaging
(and releasing...), besides being beyond my skillset, seems like a lot of
complications for an unlikely usage.
After all, the compat package could just remain an example of deriving
jexl2.
Not sure what's worth doing at this point...
--
View this message in context:
http://n4.nabble.com/JEXL-Best-way-to-generate-2-jars-tp932248p948100.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
