tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Costin Manolache" <cos...@gmail.com>
Subject Re: New EL - Split Off from Tomcat 6
Date Tue, 28 Feb 2006 22:07:32 GMT
On 2/28/06, Bill Barker <wbarker@wilshire.com> wrote:
>
>
> > -----Original Message-----
> > From: Costin Manolache [mailto:costin@gmail.com]
> > 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 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.
> >
>
> IMHO, 'maintainer' is an over statement ;-).  However, it's probably true
> that it would have trouble getting it's 3 +1s for a release in commons
> (since even commons-logging can't manage that :).  I'd be +1 to branching it
> back into Tomcat.

That's what I meant :-)


>
> > If EL has a lot of indepenent developers who are not interested in the
> > rest of tomcat ( so
> > it doesn't make sense to add them to tomcat project ) - then yes, +1
> > on splitting it
> > to a separate sub-project or jakarta-commons.
> >
>
> You could try putting a copy of EL in the Jakarta commons-sandbox, and see
> if it gets a community.  If it does, than that's probably better for
> everyone.  If it doesn't, then there would never be a release of it
> independent of Tomcat anyway.

+1 - as long as developement continues in tomcat ( i.e. the branch
that can be released )

>
> > Right now we release few packaging variations of jakarta-tomcat - IMO
> > we should start
> > releasing things like 'el', modeler, maybe standalone jasper compiler,
> > maybe standalone connector, cluster module, etc.
> >
>
> Well, a couple of projects use Jasper independently of Tomcat.  For the
> others, I don't really see the point (and Jasper is a bit under-maintained
> at the moment :).

The point for cluster and other add-on style modules would be to
reduce the size and complexity of tomcat releases, i.e. simpler is
better :-)  IMO jk could also be a separate module - i.e. have the
base tomcat only include the basic http connector, if someone is using
apache he could get the extra module.

Having independent releases of jasper / el / jspc might help if they
can be used in other projects, or if they need a more frequent release
cycle ( bug fixes, etc )

I'm just suggesting options - I'm not saying we should do it now, but
think about it for future, when it makes sense.

Costin

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


Mime
View raw message