From d2be6574a7ab5db672279ad7f952ed6b8eb66e16 Mon Sep 17 00:00:00 2001 From: Matthew Jason Benson Date: Tue, 1 Mar 2005 23:22:01 +0000 Subject: [PATCH] Fix typos. Submitted by: Larry Shatzer git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@277763 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/OptionalTasks/script.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/manual/OptionalTasks/script.html b/docs/manual/OptionalTasks/script.html index 987c37b82..dc1c247dd 100644 --- a/docs/manual/OptionalTasks/script.html +++ b/docs/manual/OptionalTasks/script.html @@ -237,13 +237,13 @@ filesizes of all files a <fileset/> caught.

</target> </project> -

We want to use the Java API. Because we donīt want always typing the package signature +

We want to use the Java API. Because we don't want always typing the package signature we do an import. Rhino knows two different methods for import statements: one for packages and one for a single class. By default only the java packages are available, so java.lang.System can be directly imported with importClass/importPackage. -For other packages you have to prefix the full classified name with Package. -For example antīs FileUtil class can be imported with -importClass(Package.org.apache.tools.ant.util.FileUtils) +For other packages you have to prefix the full classified name with Packages. +For example Ant's FileUtils class can be imported with +importClass(Packages.org.apache.tools.ant.util.FileUtils)
The <script> task populates the Project instance under the name project, so we can use that reference. Another way is to use its given name