[
https://issues.apache.org/jira/browse/JEXL-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-123:
-------------------------------
Description:
2.1 has shown it was very difficult to evolve the features without compromising
stability, i.e. respecting the contract made by the API.
3.0 main goal is to make the API stable, making clear where the difference is
between "using" Jexl and "customizing/improving" Jexl.
Since it is targeted at new projects or at least very active ones, the
development will not require Java 1.5 but will target Java6; i.e., the release
may or may not include a Java 1.5 deployable version depending on need and
contribution.
was:
2.1 has shown it was very difficult to evolve the features without compromising
stability, i.e. respecting the contract made by the API.
3.0 main goal is to make the API stable, making clear where the difference is
between "using" Jexl and "customizing/improving" Jexl.
Since it is targeted at new projects or at least very active ones, the
deployment will require at least Java 1.6.
Reworded deployment platform requirement
> Redesign API for stability
> --------------------------
>
> Key: JEXL-123
> URL: https://issues.apache.org/jira/browse/JEXL-123
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Henri Biestro
> Assignee: Henri Biestro
> Priority: Critical
> Fix For: 3.0
>
>
> 2.1 has shown it was very difficult to evolve the features without
> compromising stability, i.e. respecting the contract made by the API.
> 3.0 main goal is to make the API stable, making clear where the difference is
> between "using" Jexl and "customizing/improving" Jexl.
> Since it is targeted at new projects or at least very active ones, the
> development will not require Java 1.5 but will target Java6; i.e., the
> release may or may not include a Java 1.5 deployable version depending on
> need and contribution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
