2010/5/21 Mark Thomas <ma...@apache.org>: >> Are there any objections? > Yes. > >> The essence is that bootstrap.jar will mention tomcat-juli.jar in its >> "Class-Path" value in its MANIFEST.MF. > > This was a hack we used to keep Eclipse happy. It doesn't serve any > other purpose. >
Eclipse was just an example, that things are broking by that change. Not everybody uses catalina.bat/sh. It is just that I do not like removing features without proper justification. Besides that I know of the following: a) I am able to start Tomcat 6 by running java -jar bootstrap.jar b) JSVC documentation says to use jsvc -cp bootstrap.jar http://tomcat.apache.org/tomcat-6.0-doc/setup.html#Unix%20daemon http://tomcat.apache.org/tomcat-5.5-doc/setup.html#Unix%20daemon Though, I should say that Re: "a)": It is not an important use case. Re: "b)": There are scripts that explicitly build a CLASSPATH for jsvc, e.g. - in a recent e-mail http://marc.info/?l=tomcat-user&m=127411783204054&w=2 - found by Googling (this one is said to be for 5.0) https://wiki.ucar.edu/display/esgcet/Jsvc+Script+Example > has caused at least one > support issue for one of our customers. This sound bad. Well, if your concerns are really serious and we go this way, let's 1. Remove commons-daemon.jar reference from bootstrap.jar manifest as well. 2. Update JSVC instructions in setup.html AFAIK, the commons-daemon.jar is not needed unless we run with jsvc. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
