Re: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compilerCompiler.java

[Remy Maucherat]

Remy Maucherat wrote:

[EMAIL PROTECTED] wrote:

glenn       2002/12/31 06:01:17

  Modified:    jasper2/src/share/org/apache/jasper
                        EmbededServletOptions.java JspC.java Options.java
               jasper2/src/share/org/apache/jasper/compiler Compiler.java
  Log:
  Implement new Ant javac fork option.
  If set to true Ant forks a new process to compile JSP pages
  and does it without synchronization. Default is false.

I didn't try it (but I was looking at that in the Ant docs after the posts in tomcat-user), but there seems to be redundency in Ant, as using "extJavac" as the compier name is supposed to do the same. Since changing the compiler name is already supported, maybe adding the fork parameter was not needed.

BTW, I just found that:
<quote>
Windows Note:When the modern compiler is used in unforked mode on Windows, it locks up the files present in the classpath of the <javac> task, and does not release them. The side effect of this is that you will not be able to delete or move those files later on in the build. The workaround is to fork when invoking the compiler.
</quote>

So it could (finally) explain the mysterious JAR file locking on Windows. I think we should set to fork as the default; javac is just too risky to run in the same process ;-)

Remy


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>