Niall Pemberton wrote:
OK theres no interest in Commons here but, thinking about it, location
is minor - the real issue is about having a separatly released
artifact that other projects can depend on - which Tomcat could do
with EL. Any chance of a separate EL release (with a jar in the maven
repo)?
I'm not an EL expert by any way, but the reason there might not be any
interest, is because no one has time to take and replace an EL
implementation.
If you need additional individual JARs from tomcat published to the
repo, just let me know and I can get it done.
http://tomcat.apache.org/dev/dist/m2-repository/org/apache/tomcat/jasper-el/
I noticed today that Geronimo copied the Tomcat 6 EL implementation
[3] and now appear to be maintaing it independantly[4][5] - they have
also published it as a separate artifact[6] in the maven repo.
That is their prerogative, we don't encourage this, but the license
doesn't stop anyone from doing so.
Seems a shame to duplicate and waste effort in this way - and I can
think of quite a few projects that could benefit by plugging in the
standard EL.
I agree, we're not in a place in our development cycle to be swapping
out a library. That happens only early in a development cycle or a major
release.
We've just released a stable version, another one coming out, so stuff
like this would go to something like a 6.x where x>0.
Hope this explains it, I don't think anyone is ignoring you
Filip
Niall
[3] http://svn.apache.org/viewvc?view=rev&revision=481390
[4] http://svn.apache.org/viewvc?view=rev&revision=514550
[5] https://issues.apache.org/jira/browse/GERONIMO-2930
[6] http://tinyurl.com/2g8oek
On 2/8/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Following a discussion on Commons Dev[1] about using the independent
EL implementation associated with the JSP 2.1 spec I wondered if there
is any interest in moving what Tomcat has over to Jakarta Commons?
The motivation for all of this is it would IMO be extremely useful for
projects to be able to use/depend on an in dependant EL
project/component.
I realize that this is probably a year too late[2] and that the Tomcat
team decided to "in house" EL development and ditch Commons EL because
of problems that Commons components can have getting releases out of
the door. I would say that I believe we have improved on this in the
last year - but probably the best option would be to open up Commons
to Tomcat devs (my guess there is already some overlap already?) so
that you would have no issues committing and releasing. I would also
be prepared to to assist with or RM any EL releases.
If this is of interest I'd be happy to propose bringing in both the
code and developers to Jakarta Commons.
Niall
[1] http://tinyurl.com/yqpbnz
[2] http://tinyurl.com/32osfx
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
