On 2/28/06, Bill Barker <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Costin Manolache [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 28, 2006 9:58 AM
> > To: Tomcat Developers List
> > Subject: Re: New EL - Split Of
> -Original Message-
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 28, 2006 9:58 AM
> To: Tomcat Developers List
> Subject: Re: New EL - Split Off from Tomcat 6
>
> The most important question IMO is 'who is going to maintain
The most important question IMO is 'who is going to maintain it'. For
example - AFAIK
we are the main users and maintainer of modeler, so IMO it would make
sense to move
it back into tomcat source tree.
If EL has a lot of indepenent developers who are not interested in the
rest of tomcat ( so
it
Jacob Hookom wrote:
You can't compare a JSR spec to something like commons-logging, plus
there are people requesting that it's separate for practical use.
I meant commons-el, sorry. Being practical to others is not my problem
(esp, since it won't change much to them).
Rémy
-
You can't compare a JSR spec to something like commons-logging, plus
there are people requesting that it's separate for practical use.
Remy Maucherat wrote:
Jacob Hookom wrote:
I would like to suggest splitting EL off as a separate library from
Tomcat. The EL-API is expected to rev in it's
Jacob Hookom wrote:
I would like to suggest splitting EL off as a separate library from
Tomcat. The EL-API is expected to rev in it's own specification in the
future. It is not have any dependencies on the Servlet API or JSP API
and can be utilized in the same fashion as the commons-el projec
I would like to suggest splitting EL off as a separate library from
Tomcat. The EL-API is expected to rev in it's own specification in the
future. It is not have any dependencies on the Servlet API or JSP API
and can be utilized in the same fashion as the commons-el project.
--
Jacob Hookom
