mbenson 2005/03/01 15:22:01
Modified: docs/manual/OptionalTasks script.html
Log:
Fix typos.
Submitted by: Larry Shatzer
Revision Changes Path
1.22 +4 -4 ant/docs/manual/OptionalTasks/script.html
Index: script.html
===================================================================
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/script.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- script.html 19 Nov 2004 09:07:11 -0000 1.21
+++ script.html 1 Mar 2005 23:22:01 -0000 1.22
@@ -237,13 +237,13 @@
</target>
</project>
</pre></blockquote>
-<p>We want to use the Java API. Because we donīt want always typing the
package signature
+<p>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 <i>java</i> packages are
available, so
<i>java.lang.System</i> can be directly imported with
<code>importClass/importPackage</code>.
-For other packages you have to prefix the full classified name with
<i>Package</i>.
-For example antīs <i>FileUtil</i> class can be imported with
-<code>importClass(<b>Package</b>.org.apache.tools.ant.util.FileUtils)</code>
+For other packages you have to prefix the full classified name with
<i>Packages</i>.
+For example Ant's <i>FileUtils</i> class can be imported with
+<code>importClass(<b>Packages</b>.org.apache.tools.ant.util.FileUtils)</code>
<br>
The <code><script></code> task populates the Project instance under
the name <i>project</i>, so we can use that reference. Another way is to use
its given name
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
