I think that most linux packagers don't work with Java projects and do whatever they like. What Daniel is experiencing is an overzealous packager that shuts down the most basic service tomcat needs to provide: run a web application that does more than serve static pages. Packagers often make any documentation that is available for a Java project worthless because they move everything all over the disk. This is akin to a mysql installation where you can't start a database and run queries against.
Also, AFAIK 5.5.20 is about 1.5 years old. To me that is an indication that packagers don't provide the most secure and workable solution, especially when the latest 5.5.x (5.5.25) is already 6 months out. Conservatism is a great thing for production servers, but running 1.5 years behind the curve...? Of course, the converse could be said for Java developers not getting linux packaging, and in a sense we can learn a great deal from the tried and tested unix package management. But even that is something that is still evolving. For instance maven's repository infrastructure could (should?) be pushed to a RPM/jpackage/apt service. The way I see it is that maven has reinvented the wheel, and managed to make it a bit bumpier... Martijn On 1/21/08, C. Bergström < [EMAIL PROTECTED]> wrote: > > > On Mon, 2008-01-21 at 12:13 +0100, Martijn Dashorst wrote: > > So your advise is to run a *very* outdated version because the packagers > > > haven't updated their software? > > Sounds like a great way to open up your system to hackers. > > That's a very broad and sweeping statement. > > 1) I'm sure if there were known issues the distro package > maintainer > *should* issue an update with a fix > 2) Looking at http://tomcat.apache.org/whichversion.html it > appears 5.x > is still supported > > I'll agree that a best practice to use latest stable, but not all > organizations get it right living on the bleeding edge of custom > packages and SVN Trunk or CVS HEAD if you prefer.. > > I'm trying to give sensible advice that is generic enough to not lead > someone astray or with other caveats which could result in bad pratices > or more problems down the road. > > Now if I look at his original email and wonder why deb is still on > 5.5.20-2etch1 when the apache site lists 5.5.25 as current I have no > idea. > > ./C > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0
