Jacob Kjome wrote:

I don't know about anyone else, but I avoid using installer programs on Windows to avoid exactly this intrusive behavior.  I don't want anyone other than myself modifying my system classpath variable.  Classpath issues are problematic enough without having some external entity polluting the classpath and causing library versioning problems.

Either use a batch file wrapper or use Class-Path entries in the MANIFEST.MF file. Eg...

Class-Path: jar1.jar jar2.jar other/jar3.jar


Jake

I agree.  My preference is to use a batch file whenever possible, however the ability for some users to create directories and unzip a file is sometimes too much to ask.  An installer definitely has its benefits for these situations!
--
   Anthony Rabaa
   Software Developer & Network Administrator
    AMCon Research Inc.
    Ottawa, Ontario, Canada
    http://www.amconresearch.net

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to