On 4/8/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
The Taglibs project has been dead for years. I'm sure it's not going
to improve; taglibs are a pain to implement (especially if support is
targeting older JSP specs), JSTL replaced many and at the same time
JSP stopped being the obvious choice for web applications. It's
frustrating to both users and committers to have the project sitting
with doors apparently open, so I'd like to suggest a closing up of
shop.
Here's what I'm thinking:
1) Standard Taglib 1.1.3 release. This is getting pretty close, so it
would be very nice to get a release out.
<snip/>
Sure would be nice, the last Taglibs release (RDC 1.0) was ~20 months ago.
2) RDC Taglib needs to continue. It's not had a lot of activity
recently, but I'm presuming that Rahul is still active on this one and
that it would need to continue. My suggestion is that it joins Jakarta
Commons (either at jakarta.apache.org/commons or commons.apache.org if
Commons moves there). Its build system could be brought up to date
too.
<snap/>
Your assessment is correct. I'm fine with your suggestion as well,
though at some point, we'll need to bring this up concretely with the
jao/c or cao folks. Perhaps waiting for the cao dust to settle might
be reasonable. I will volunteer to wrestle m2 when necessary.
3) Others would be end of lifed - with a request going out to find out
which ones are strongly active. I would still like to coalesce many
into the sandbox'd Unstandard Taglib, ie) a single taglib with various
bits of value that JSTL did not replace (and making it JSP 2.0 or 2.1
specific); so I am interested in hearing which functionalities are
valuable.
<snip/>
Agreed on the moving to 2.0 / 2.1 bit. I do not intend to spend any
time on < 2.0 taglibs, which is all of Taglibs Proper ATM (if we leave
JSTL in a class of its own).
-Rahul
Target date for all of this would be the end of this year.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
