jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felipe Leme <jakartalis...@felipeal.net>
Subject [vote] dbtags 1.0.0 and random 1.0.2
Date Fri, 05 Mar 2004 19:10:35 GMT
Hi all,

I closed a lot of dbtags last week (actually, most of them were related
to the same problem -
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26863), so I think
it's time for a dbtags-1.0.0 release (latest release is 1.0B1, from aug
21st, 2001).

Although JSTL's SQL replaced most of DBTags features, people still uses
the later. In fact, it is not really clear that DBTags shouldn't be used
anymore. So here is my proposal:

- mark the 2 remaining bugs as LATER
- put a warning on the main doc page stating something like this:

If you are using a recent implementation of the 
Servlet specification, you should use Apache's
implementation of the JSTL, not DBTags.  DBTags has
been inactive since development on JSTL began, and it
should be considered deprecated for Servlet 2.3 or 2.4
- update the rest of the documentation (including state of union)
- release 1.0.0, as the "final" DBTags release (assuming that now people will be using JSTL
SQL more and more)

[ ] +1 Release dbtags-1.0.0
[ ] -0 Do not release, please explain why

NOTE: un fact, I think we should create a new category of taglibs that
are neither deprecated nor supported. Something like obsolete (i.e. the
taglib is still supported for JSP 1.1 containers, but it can be replaced
for other taglibs in a JSP 1.2 and JSP 2.0). Many of the supported
taglibs would fit in this category: dbtags, XTags, Strings, page,
application, etc... (anyway, that's a subject for another message)

Similarly, I fixed one bug on random and realized some others bug were
fixed between 1.0.1 and now

[ ] +1 Release random-1.0.2
[ ] -0 Do not release, please explain why



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

View raw message