On Fri, 17 May 2002, Remy Maucherat wrote:
Date: Fri, 17 May 2002 10:59:00 -0700
From: Remy Maucherat [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: Re: Switching javac for jasper 2
On Fri, 17 May 2002, Kin-Man
See below.
Date: Thu, 16 May 2002 14:07:36 -0700 (PDT)
From: [EMAIL PROTECTED]
Subject: Re: Switching javac for jasper 2
X-X-Sender: [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED], Kin-Man Chung
[EMAIL PROTECTED]
MIME-version: 1.0
Delivered-to: mailing list [EMAIL
On Fri, 17 May 2002, Kin-Man Chung wrote:
com.sun.tools.javac.Main doesn't seem to be in JDK1.2.x, and that's the
target platform, isn't it ?
I believe for 4.1.x, it should be 1.3.1 and above. Like I said, 1.2
javac is currently unsupported and deprecated in 1.3 and 1.4, and
On Fri, 17 May 2002, Kin-Man Chung wrote:
I think the best solution for javac is to just bundle ant.jar and
use it programmatically ( i.e. new Javac(), etc ). The introspection
and hacks required to support multiple compilers are just too
ugly - and they already have good solutions
Tomcat has been using sun.tools.javac.Main as the default java compiler
for compiling the java files generated by Jasper. This compiler is
essentially a JDK1.2 compiler, current deprecated and unsupported.
The warning message Note: sun.tools.javac.Main has been deprecated
is probably familiar to
com.sun.tools.javac.Main doesn't seem to be in JDK1.2.x, and that's the
target platform, isn't it ?
I think the best solution for javac is to just bundle ant.jar and
use it programmatically ( i.e. new Javac(), etc ). The introspection
and hacks required to support multiple compilers are just
