Re: EL and JSP 2.1

[Remy Maucherat <re...@apache.org>]

Mark Thomas wrote:
>>The key questions are:
>> - does 6.0.x become the main development branch?
> 
> Yes. We did this for 5.5.x and it worked.

Ok.

>> - do we merge jasper and container?
> 
> No. Good to keep them independent.

Ok.

>> - do we merge build and container
> 
> Maybe. If someone wants to take the time to do this and update the
> build scripts great. Personally, not an itch I feel the need to scratch.

The JSP implementation is independent, so there's no change here.

>> - do we maintain servletapi for 6.0?
> 
> No for the api stuff proper. We don't host it, can't change it and our
> own implementation would be more trouble than it is worth.
> 
> Maybe for the examples. It is useful to be able to fix problems with
> them. The examples could always be merged in with the container module.

I think we should have an implementation of the new API.

Rémy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

Re: EL and JSP 2.1

[Ian Darwin <ia...@darwinsys.com>]

>>> - do we maintain servletapi for 6.0?
>>
>>
>> No for the api stuff proper. We don't host it, can't change it and our
>> own implementation would be more trouble than it is worth.
>>
>> Maybe for the examples. It is useful to be able to fix problems with
>> them. The examples could always be merged in with the container module.
>
>
> I think we should have an implementation of the new API.
>
Does it need to be maintained as its own tree with its own JavaDoc? Or,
if it is "only" something to compile against, could we just extract it from
the compiled classes, using reflection? 

Ian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org