2012/10/1 Mark Thomas <ma...@apache.org>: > In the two+ years since Taglibs moved to the Tomcat project there have > been a few short bursts of activity totalling just over 200 commits but > no releases. (...) > > Note: This is intended as a discussion topic - not a formal proposal/vote. >
Regarding the two taglibs that are not yet in the attic, I have no interest in "RDC" taglib, but I am interested in JSTL one. I think once we make the first release, things should go easier after that. A few notes after quick review of the sources: 1. Can we go up from Java 5 and require/use at least Java 6 to build the project? I am even OK to be brave and go up to Java 7. I do not like Java 5, because a) It is outdated. It would be strange for a "new" project to use that if we are going to support it for long. b) It is not opensource. OpenJDK is since Java 6. The version of Java is important for this class, that implements javax.sql.DataSource: \standard\impl\src\main\java\org\apache\taglibs\standard\tag\common\sql\DataSourceWrapper.java Java 7 will allow us to support a later version of JDBC and will allow this project to build on Gump. 2. Apparently, there are two implementations for JSTL 1.0 tags: "jstlel", "compat". "jstlel" provides its own EL engine according to the old specification, "compat".uses EL engine from the container. I think having two implementations is too many. Can we drop "compat"? I have not studied the history yet, but my copy of jakarta-taglibs-standard-1.1.2 does not have those "compat" tags neither in binary nor in source distributive. 3. The README_*.txt files in the root directory are outdated and need some tweaking. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
