diff --git a/manual/Types/antlib.html b/manual/Types/antlib.html index 925320ae7..0e738c053 100644 --- a/manual/Types/antlib.html +++ b/manual/Types/antlib.html @@ -17,13 +17,13 @@
- +The name space URIs with the pattern antlib:java package are given special treatment. @@ -152,14 +152,14 @@
The requirement that the resource is in the default classpath - may be removed in future versions of Ant.
+ may be removed in future versions of Ant. -- If you want to separate the antlib from your local Ant installation, e.g. because you - want to hold that jar in your projects SCM system, you have to specify a classpath, so + If you want to separate the antlib from your local Ant installation, e.g. because you + want to hold that jar in your projects SCM system, you have to specify a classpath, so that Ant could find that jar. The best solution is loading the antlib with <taskdef>.
@@ -168,7 +168,7 @@ <taskdef uri="antlib:net.sf.antcontrib" resource="net/sf/antcontrib/antlib.xml" classpath="path/to/ant-contrib.jar"/> - + <target name="iterate"> <antcontrib:for param="file"> <fileset dir="."/> @@ -181,10 +181,7 @@- - - -
Definitions defined in antlibs may be used in antlibs. However the namespace that definitions are placed in are dependent on @@ -258,9 +255,6 @@ </project> - - - diff --git a/manual/Types/assertions.html b/manual/Types/assertions.html index e168969fd..9942b4c7d 100644 --- a/manual/Types/assertions.html +++ b/manual/Types/assertions.html @@ -24,22 +24,22 @@
-
The assertions type enables or disables the Java 1.4 assertions feature,
on a whole Java program, or components of a program. It can be used
in <java>
and
-<junit>
to add extra validation to code.
+<junit>
to add extra validation to code.
-Assertions are covered in the +Assertions are covered in the Java SE documentation, and the Java Language Specification.
The key points to note are that a java.lang.AssertionError -is thrown when an assertion fails, and that the facility is only available +is thrown when an assertion fails, and that the facility is only available on Java 1.4 and later. To enable assertions one must set source="1.4" (or later) in <javac> when the source is being compiled, and that the code must contain assert statements to be tested. The @@ -47,20 +47,16 @@ result of such an action is code that neither compiles or runs on earlier versions of Java. For this reason Apache Ant itself currently contains no assertions.
-When assertions are enabled (or disabled) in a task through nested -assertions elements, the class loader or command line is modified with the +When assertions are enabled (or disabled) in a task through nested +assertions elements, the class loader or command line is modified with the appropriate options. This means that the JVM executed must be a Java 1.4 or later JVM, even if there are no assertions in the code. Attempting to -enable assertions on earlier VMs will result in an "Unrecognized option" -error and the JVM will not start. +enable assertions on earlier VMs will result in an "Unrecognized option" +error and the JVM will not start.
- - -
-Attribute | Description | @@ -75,7 +71,7 @@ error and the JVM will not start.
Attribute | Description | @@ -113,7 +109,7 @@ If neither a package nor class is specified, assertions are turned on in all< Disable assertions in portions of code. -
Attribute | Description | @@ -138,7 +134,6 @@ Disable assertions in portions of code. Because assertions are disabled by default, it only makes sense to disable assertions where they have been enabled in a parent package. -