Comment 6 for bug 207787

David,

Great suggestions. I've actually abandoned the Tomcat 5.5 project and I've also stopped using all of the Tomcat packages in the repositories. The Tomcat packages in the repository are completely invalid. If you download Tomcat from Apache and compare it to the Tomcat from the repository packages, they contain different JAR files and this causes major issues with some applications. Tomcat specifically repackages certain libraries from Apache Commons to avoid naming and version conflicts. The Tomcat packages from the repositories use the Apache Commons libraries instead and this is incorrect.

Rather than continue using Tomcat 5.5 and keeping my scripts up to date, I've written a new set of packages for Tomcat 6 that do a number of things differently.

  - First, they install a correct version of Tomcat that is identical to the version downloaded from Apache

  - Second, it provides a very clean install that makes it much simpler to update. My previous scripts assumed you were installing the packages from the repositories and then really moved things around. This caused major issues with updates.

  - Third, the new packages are completely based on multiple instances. This is much better because it can support a single instance or multiple instances without any issues.

  - I use much more standard locations for everything now.

Here's the thread over at the forums about these new packages:

    http://ubuntuforums.org/showthread.php?t=1211517

I'd like to see this packages incorporated into the main repositories once they are cleaned up some. I love the options you have added to your new_instance scripts and would welcome your assistance with adding those to my packages. I much prefer using a separate script for removing instances to reduce confusion. However, if the script was named tomcat6_manager.sh or something like that, it would be okay. 2 scripts still seems better though.