https://bz.apache.org/bugzilla/show_bug.cgi?id=69262
--- Comment #4 from skylar.sut...@gmail.com --- If the Tomcat team thinks that is the best solution - sure. The root issue is that the community needs JSTL tags, but there is no Apache JSTL compatible with Jakarta (because the JSTL project was moved to the Apache Attic).. so the community recommendation is to use a mixed bag of Glassfish JSTL + Tomcat container. Using the Glassfish JARs is what brings the jakarta.el-api into the classpath. Having an Apache JSTL that is Jakarta compliant would solve that issue. (TBH, I'm kind of surprised I'm the first one to report this... but maybe I'm not and I just didn't find the other reports in my search). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org