Kalle Kivimaa wrote:
Why not simply depend on libtomcat4-java? Is it that big a package?
It's a bit strange having Jetty depend on libtomcat - simply from a naming perspective. Kind of like having postgres depend on mysql.
There is also may be a good reason to split out jasper, from a versioning point of view - as there are many users that wish to stick with old jasper1 (for assorted bad reasons) and they may also wish to do so when the next upgrade to the 1.2 JSP spec.
Stefan Gybas wrote:
tomcat4 just activates all webapps in this directory when it's started. Other servlet engines can do the same.
Will the Jetty package need to indicate that it conflicts with the tomcat package - so that it two copies of each webapp do not get started (and both servers try to grab port 80 or 8080).
Maybe the installation scripts should try to detect other servlet servers installed and offer an option not to auto start?
cheers
-- Greg Wilkins<[EMAIL PROTECTED]> Phone/fax: +44 7092063462 Mort Bay Consulting Australia and UK. http://www.mortbay.com
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
