Abel Braaksma wrote:
In reality, in Windows, it is more something like:
1. For a windows executable it must be in the path to be executed, for a
jar file it must be in the ext dir
...
Is this far more complex than a traditional Java jar file? You better
believe it ;-)
Actually no. There are two critical differences:
1. Once the Windows executable is properly configured, you don't have to
do it again. You have to rearrange the JAR file every time you change
directories.
2. There aren't multiple paths to deal with. There are multiple
classpaths and jre/lib/ext directories to deal with.
Well, I grew up with Windows 3.0, MS DOS before that etc, so I am lucky
to understand why it is so and how to change these settings. But many
aren't. I am not saying that things in Java world are easy, but I
consider it far from reality to say things are easy in Windows (or Unix)
environments.
Actually Unix is pretty good. I believe on my Mac I just type "xsltproc"
and I'm done. Possibly at some point I had to do "sudo fink install
libxslt" but I don't think I even had to do that. Linux would probably
use apt-get instead. Otherwise it's much the same.
--
Elliotte Rusty Harold elharo(_at_)metalab(_dot_)unc(_dot_)edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--