Any reason you've chosen Tomcat over Jetty?
Because we know how to embed Tomcat :) But after your suggestion I try to look around and find more information about Jetty.
Why would a user care if they ran a supa uber jar vs. unpacking and stuffing around with script files etc.
Standard procedure for almost every program (as far as Java is considered: Ant, Maven, JBoss etc.):
1. Get the tarball. 2. Unpack it to usual directory. 3. ln -s ~/usual_directory/app_dir/bin/run-script.sh ~/bin/ 4. Use every day with simply calling run-script.sh.
(Non)standard procedure when getting uberjar:
1. Oh! Sweet! Only single jar, no documentation, this must be super! 2. ...but how do I run this? 3. So I still need to download the documentation? And it's in separated package?! 4. Download the documentation... Read it. 5. Ah... "java -jar xxx-uber.jar" 6. Where to place it? ...I know, I make a special directory for it!!! 7. First run: java -jar ~/usual_directory/app_dir/xxx-uber.jar 8. Second run: java -jar ~/usual_directory/app_dir/xxx-uber.jar 9. Third run: java -jar ~/... blah! I'm must write a script for it! 10.Write run-script.sh 11.Place it in ~/bin/ 12.Call run-script.sh. 13.Check why it doesn't work 14.Fix the typos. 15.Use every day with simply calling run-script.sh.
I know this is a sarcastic, but some kind of packaging plugin realy would be useful. How is the packaging of Maven done?
And another thing... When embedding Tomcat I need to manualy provide it with path to application.war (or unpacked directory). How to do that when all is in a single uberjar?
-- _____________________________________________ Lukasz Piestrzeniewicz System Engineer Ericpol Telecom sp. z o.o. Sienkiewicza 85/87, 90-057 Lodz, Poland e-mail: [EMAIL PROTECTED] mobile: +48 504488735 tel: +48 42 6353619 fax: +48 42 6315555 http://www.ericpol.pl/ _____________________________________________
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
