Tim, Thank you very much for the info. For now at least I will make sure our Jasper package is kept in sync with Tomcat releases.
On Sat, 2006-08-19 at 19:36 -0400, Tim Funk wrote: > In different versions of Tomcat, Jasper could change "a lot" since its > not a "public api". But it's cool for other apps to use it right? It seems Jetty uses Tomcat's Jasper. > The servlet api could also change in different Tomcat revisions too. But > these changes are usually VERY minor and due to corrections/errata found > in the spec. Ok, might just revision bump it as well with Tomcat to be safe, or go monitor the spec changes and etc :) > Typically - when Tomcat changes - there was usually a change in Jasper > too. So any Tomcat release would require a Jasper release. But there > might or might NOT be a servlet api change. Great, that at least gives me some idea of how to maintain those other packages. It seems that Jasper will always be somewhat bound to Tomcat. So no hope of it being packaged or etc on it's own. Hopefully servlet api can, because in 2.4's case it seems to be the only available much less open source implementation. Allot of packages use it. -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part