Re: Relation of jasper and servlet API to Tomcat
If you want to include the real tomcat in gentoo - please use the official label, follow the same procedure as our release, and make sure the result of emerge is identical with what the user would get if he would get tomcat from ASF. If you have to patch - and the patch alters the structure or behavior - please don't call the result 'tomcat' :-) Costin On 8/19/06, William L. Thomson Jr. [EMAIL PROTECTED] wrote: 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
Re: Relation of jasper and servlet API to Tomcat
On Sun, 2006-08-20 at 13:43 -0700, Costin Manolache wrote: If you want to include the real tomcat in gentoo - please use the official label, follow the same procedure as our release, We do include the real Tomcat. Problem is aspects of Tomcat many other apps use. With regard to Jasper I believe it's just Jetty. But servlet-api, a bunch of packages depend on that one. How we version the servlet-api is still up for discussion. Since it's not really based on Tomcat versions. Jasper is another story, and Jasper's package version is likely to stay that of the version of Tomcat it came from. Source wise. and make sure the result of emerge is identical with what the user would get if he would get tomcat from ASF. For the most part were are there, short of one jar, naming-factory-dbcp.jar. However it's possible that Tomcat's on Gentoo could be built with newer versions of dependencies/bundled jars. If you have to patch - and the patch alters the structure or behavior - please don't call the result 'tomcat' :-) We do not modify Tomcat at all. The only patches are to like not download/compile etc jars that are dependencies of Tomcat, or will be bundled. We link those in since they will already exist on the system as a dependency of Tomcat. Beyond that the only thing the patches do is modify/exclude some targets. Since they lack any sort of condition that would allow a command line option for ant to control if those aspects are built. Like examples, docs, etc. We have use flags, if someone does not set examples, docs etc. We do not build/compile that stuff, much less install it. So our patches do not really modify Tomcat at all. Slight modifications to build.xml files only, and to control what get's built when, how, and with what. -- William L. Thomson Jr. Gentoo/Java signature.asc Description: This is a digitally signed message part
Re: Relation of jasper and servlet API to Tomcat
In different versions of Tomcat, Jasper could change a lot since its not a public api. 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. 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. -Tim William L. Thomson Jr. wrote: First off, is there any reason Jasper and Servlet-API can't be projects of their own? With their own binary releases. Reason I ask is that it seems other apps use Jasper, not just Tomcat. With regard to servlet-api, it seems to be the only open source implementation. Sun has yet to release 2.4, only 2.3. So the only 2.4 servlet api I can find is the one in Tomcat. On Gentoo we have 3 packages built from the same Tomcat sources. If Tomcat has a revision bump, does that mean Jasper or Servlet API changes as well? If so we have to revision bump 3 packages instead of just Tomcat. Also if I make a patch for servlet-api for Tomcat, the same patch also applies to the servlet API package as well. So multiple copies of the same patch. Much less if someone emerges both servlet api and Tomcat they end up with two copies. Which sorta defeats what we do on Gentoo. Which is to install a resource like log4j, commons stuff etc, once, and symlink it where ever it's needed or used. So you don't end up with different versions and multiple copies of jars and etc all over the place. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Relation of jasper and servlet API to Tomcat
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
Relation of jasper and servlet API to Tomcat
Greetings, Over the past 7+ months I have been maintaining Tomcat on Gentoo. I have now become a Gentoo developer so I can officially become the Tomcat maintainer on Gentoo. With that said, I have a couple of things I am curious about. First off, is there any reason Jasper and Servlet-API can't be projects of their own? With their own binary releases. Reason I ask is that it seems other apps use Jasper, not just Tomcat. With regard to servlet-api, it seems to be the only open source implementation. Sun has yet to release 2.4, only 2.3. So the only 2.4 servlet api I can find is the one in Tomcat. On Gentoo we have 3 packages built from the same Tomcat sources. If Tomcat has a revision bump, does that mean Jasper or Servlet API changes as well? If so we have to revision bump 3 packages instead of just Tomcat. Also if I make a patch for servlet-api for Tomcat, the same patch also applies to the servlet API package as well. So multiple copies of the same patch. Much less if someone emerges both servlet api and Tomcat they end up with two copies. Which sorta defeats what we do on Gentoo. Which is to install a resource like log4j, commons stuff etc, once, and symlink it where ever it's needed or used. So you don't end up with different versions and multiple copies of jars and etc all over the place. Ideally it would be great if Jasper and Servlet API were on their own. Different sources and binary releases. Then they could be bundled with releases of Tomcat just as other stuff is bundled. That would make more sense if Tomcat specific things changed among revisions, but did not change Jasper or servlet api stuff. If this has already been discussed, is in the works or etc. I apologize for not seeing it, or being aware of it. -- William L. Thomson Jr. Gentoo/Java signature.asc Description: This is a digitally signed message part
