Download Apache Ant 1.5.4 Manual

Ant Manual 1.5.4
12/9/2003 7:47 PM
package
Name of the destination package for generated java classes.
No
compiler
class name of a JSP compiler adapter, such as "jasper" or
"jasper41"
No -defaults to
"jasper"
ieplugin
mapped
Java Plugin classid for Internet Explorer.
No
(boolean) Generate separate write() calls for each HTML line in No
the JSP.
classpath
The classpath to use to run the jsp compiler. This can also be
specified by the nested element classpath Path).
classpathref
A Reference. As per classpath
failonerror
uribase
flag to control action on compile failures: default=yes
No
The uri context of relative URI references in the JSP pages. If it No
does not exist then it is derived from the location of the file
relative to the declared or derived value of uriroot.
The root directory that uri files should be resolved against.
No
uriroot
compiler
Class name of jsp compiler adapter to use. Defaults to the
standard adapter for Jasper.
No, but it seems to
work better when
used
No
No
compilerclasspath The classpath used to find the compiler adapter specified by
No
the compiler attribute.
webinc
Output file name for the fraction of web.xml that lists servlets. No
webxml
File name for web.xml to be generated
No
The mapped option will, if set to true, split the JSP text content into a one line per call
format. There are comments above and below the mapped write calls to localize where in
the JSP file each line of text comes from. This can lead to a minor performance degradation
(but it is bound by a linear complexity). Without this options all adjacent writes are
concatenated into a single write.
The ieplugin option is used by the <jsp:plugin> tags. If the Java Plug-in COM Class-ID
you want to use changes then it can be specified here. This should not need to be altered.
uriroot specifies the root of the web application. This is where all absolute uris will be
resolved from. If it is not specified then the first JSP page will be used to derive it. To derive
it each parent directory of the first JSP page is searched for a WEB-INF directory, and the
directory closest to the JSP page that has one will be used. If none can be found then the
directory Jasperc was called from will be used. This only affects pages translated from an
explicitly declared JSP file -including references to taglibs
uribase is used to establish the uri context of relative URI references in the JSP pages. If it
does not exist then it is derived from the location of the file relative to the declared or
derived value of uriroot. This only affects pages translated from an explicitly declared JSP
file.
Parameters specified as nested elements
This task is a directory based task, like javac, so the jsp files to be compiled are located as
java files are by javac. That is, elements such as includes and excludes can be used directly
inside the task declaration.
Elements specific to the jspc task are:classpath
222/305