A jar-file just contains the classes and other files of your application.
This concept still expects a Java-VM at the target machine and a call of a
method inside of the jar. So you cannot deliver a self-installing
application by just putting all your classing into a jar.

Roman 

> Von: Matt Harrington <matt / msg.ucsf.edu>
> Antworten an: ruby-talk / netlab.co.jp
> Datum: Sun, 17 Dec 2000 06:22:48 +0900
> An: ruby-talk / netlab.co.jp (ruby-talk ML)
> Betreff: [ruby-talk:7470] Re: Packaging Ruby
> 
> On Fri, Dec 15, 2000 at 09:52:22PM +0900, Aleksi Niemelwrote:
> 
>> Having said that, I wonder if it would be a problem to write an utility
>> which grabs all the used libraries and produces a "local copy version" of
>> them. Which in turn could be packaged by various tools and shipped to
>> "customer".
> 
> Something like Java's "jar" utility would be nice.
> 
> ---Matt
>