remm 2003/01/01 07:26:34 Modified: webapps/docs jasper-howto.xml Log: - Due to continued problems with javac, I think fork should default to true. Revision Changes Path 1.4 +6 -3 jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml Index: jasper-howto.xml =================================================================== RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- jasper-howto.xml 31 Dec 2002 14:48:44 -0000 1.3 +++ jasper-howto.xml 1 Jan 2003 15:26:34 -0000 1.4 @@ -116,7 +116,7 @@ <li><strong>fork</strong> - Have Ant fork JSP page compiles so they are performed in a seperate JVM from Tomcat? <code>true</code> or -<code>false</code>, default <code>false</code>.</li> +<code>false</code>, default <code>true</code>.</li> <li><strong>javaEncoding</strong> - Java file encoding to use for generating java source files. Default <code>UTF8</code>.</li> @@ -159,10 +159,13 @@ <li><strong>fork</strong> - The internal JVM javac compiler used by Ant has a known memory leak. And Ant requires that java compiles be synchronized, i.e. only one JSP page can be compiled at a time. Set fork to -<code>true</code> so that Ant compiles JSP pages in a seperate JVM. +<code>true</code> or do not define it (it is the default value) so that Ant +compiles JSP pages in a seperate JVM. This removes the synchronization of JSP page compiles and prevents all the javac classes from being instantiated and subsequently garbage -collected by the JVM Tomcat is running in.</li> +collected by the JVM Tomcat is running in. This also works around known +issues with javac, including memory leaking, as well as JAR file locking +on Windows.</li> </ul> </p>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
