> I tried it on W2K Jdk 1.5.0_06.
> I got an error message about the jar not existing.
On 13 Jan 2006 23:50:54 -0800, "Jean-Francois Briere"
<jfbriere@gmail.com> wrote, quoted or indirectly quoted someone who
said :
>Which is normal because the specified jar is not seen as the archive
>name (since there is no 'f' option) but as one file to be inputted into
>the archive.
>And since this file does not exist, you have the error message.
what do you think the jar designers were up to without making you
specify a jar name? They make it the exception case TO specify it.
Jar creation output to the console is just gibberish.

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
Thomas Hawtin - 14 Jan 2006 17:27 GMT
> what do you think the jar designers were up to without making you
> specify a jar name? They make it the exception case TO specify it.
> Jar creation output to the console is just gibberish.
jar just follows the conventions of tar (Tape ARchive). tar was designed
to have the result streamed to a tape drive (possibly through a
compression program). From jar's point of view, the output is not to the
console, but to the standard output. It's a very normal way of handling
things under UNIX.
Tom Hawtin

Signature
Unemployed English Java programmer
http://jroller.com/page/tackline/