From b1a83d53e5bcf341711001059540099ae5009ad3 Mon Sep 17 00:00:00 2001 From: Jan Materne Date: Mon, 26 Feb 2007 14:47:26 +0000 Subject: [PATCH] Some more words about not-using this task. More focus on its deprecation. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@511828 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/OptionalTasks/jspc.html | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/manual/OptionalTasks/jspc.html b/docs/manual/OptionalTasks/jspc.html index 3ccda86eb..fb3428c88 100644 --- a/docs/manual/OptionalTasks/jspc.html +++ b/docs/manual/OptionalTasks/jspc.html @@ -24,7 +24,7 @@ -

jspc

+

jspc (deprecated)

Description

Ant task to run the JSP compiler and turn JSP pages into Java source. @@ -33,11 +33,17 @@ compiler, you should seriously consider using the task shipping with Tomcat instead. This task is only tested against Tomcat 4.x. There are known problems with Tomcat 5.x that won't get fixed in Ant, please -use Tomcat's jspc task instead.

+use Tomcat's jspc task instead.
+Instead of relying on container specific JSP-compilers we suggest deploying +the raw files (*.jsp) and use the container build-in functions: after deploying run +a test suite (e.g. with Cactus or +HttpUnit) against the deployed web +application. So you'll get the test result and the compiled JSPs. +

-It can be used to precompile JSP pages for fast initial invocation +This task can be used to precompile JSP pages for fast initial invocation of JSP pages, deployment on a server without the full JDK installed, or simply to syntax check the pages without deploying them. In most cases, a javac task is usually the next stage in the build process.