Users that have manually managed their CLASSPATH can run into problems when they have alternate versions of Narwhal's "jars". At the moment, the Rhino bootstrapping process inherits the CLASSPATH environment and only augments it with its js.jar and jsline.jar. To improve first impressions of Narwhal, we should overwrite CLASSPATH and inherit NARWHAL_CLASSPATH if a user has very deliberately asked for jars to be installed at bootstrapping time. Package jars would still be loaded automatically with a dynamic class loader, obviating the need for NARWHAL_CLASSPATH in most cases.
tlrobinson
commented
15 years ago
Users that have manually managed their CLASSPATH can run into problems when they have alternate versions of Narwhal's "jars". At the moment, the Rhino bootstrapping process inherits the CLASSPATH environment and only augments it with its js.jar and jsline.jar. To improve first impressions of Narwhal, we should overwrite CLASSPATH and inherit NARWHAL_CLASSPATH if a user has very deliberately asked for jars to be installed at bootstrapping time. Package jars would still be loaded automatically with a dynamic class loader, obviating the need for NARWHAL_CLASSPATH in most cases.