From 364fc015253b0019412fefff31e935d64174d015 Mon Sep 17 00:00:00 2001 From: Peter Reilly Date: Tue, 12 Dec 2006 23:39:41 +0000 Subject: [PATCH] document the issues with using script/classpath to load javascript implementation git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@486416 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/OptionalTasks/script.html | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/docs/manual/OptionalTasks/script.html b/docs/manual/OptionalTasks/script.html index 102df2568..53f3c1fe7 100644 --- a/docs/manual/OptionalTasks/script.html +++ b/docs/manual/OptionalTasks/script.html @@ -134,14 +134,23 @@ Groups@Google: "Rhino, enum.js, JavaAdapter?" by Norris Boyd in the newsgrou path-like structure and can also be set via a nested <classpath> element.

- If a classpath is set, it will be used as the current thread context classloader, and - as the classloader given to the BSF manager. This means that it can be used to specify - the classpath containing the language implementation. This can be usefull if one wants - to keep ${user.home}/.ant/lib free of lots of scripting language specific jar files. + If a classpath is set, it will be used as the current thread + context classloader, and + as the classloader given to the BSF manager. + This means that it can be used to specify + the classpath containing the language implementation for BSF + or for JSR 223 managers. + This can be usefull if one wants + to keep ${user.home}/.ant/lib free of lots of scripting language + specific jar files.

- NB: This classpath cannot (currently) be used to specify the location of - the BSF jar file. + NB: This classpath cannot (currently) be used to + specify the location of + the BSF jar file. Also, due to classloading issues, languages + that have engines in the BSF jar file cannot have the + implementation in the classpath element. This includes the + javascript, jython, netrexx and jacl languages.

Examples