I vote for your solution. That is, after all, why the funcitonality exists :~)
--
Geoff Granum
[EMAIL PROTECTED]
Aeronautical & Astronautical Engineering,
Purdue University
West Lafayette, Indiana
On Mon, 18 Aug 2003 12:26:35 -0500, Jacob Kjome <[EMAIL PROTECTED]> 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
