Return-Path: Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 89471 invoked from network); 30 Nov 2000 16:05:05 -0000 Received: from unknown (HELO harry.runtime-collective.com) (mail@212.42.168.25) by locus.apache.org with SMTP; 30 Nov 2000 16:05:05 -0000 Received: from percy.runtime-collective.com ([10.0.0.11] ident=mail) by harry.runtime-collective.com with esmtp (Exim 3.12 #1 (Debian)) id 141WJV-0002hn-00 for ; Thu, 30 Nov 2000 16:12:01 +0000 Received: from localhost ([127.0.0.1] helo=runtime-collective.com ident=faith) by percy.runtime-collective.com with esmtp (Exim 3.16 #1 (Debian)) id 141WGw-0007zw-00 for ; Thu, 30 Nov 2000 16:09:22 +0000 Sender: faith Message-ID: <3A267BB1.70D24B2F@runtime-collective.com> Date: Thu, 30 Nov 2000 16:09:21 +0000 From: Joe Faith Organization: Runtime Collective, Ltd. X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.18pre21 i686) X-Accept-Language: en MIME-Version: 1.0 To: ant-user@jakarta.apache.org Subject: Re: Cannot use classic compiler, as it is not available References: <3A267658.834ABB45@runtime-collective.com> Content-Type: multipart/alternative; boundary="------------41AA2ABD05095B457217E859" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N --------------41AA2ABD05095B457217E859 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stefan, all present and correct. Yours, still baffled Joe -------------------------------- ant Searching for build.xml ... Buildfile: /home/faith/treeDev/build.xml prepare: compile: /home/java/jakarta-ant/lib/ant.jar:/home/java/jakarta-ant/lib/jaxp.jar:/home/java/jakarta-ant/lib/parser.jar:/home/java/jdk1.2.2/lib/tools.jar [javac] Compiling 4 source files to /home/faith/treeDev/tomcat/webapps/tree/WEB-INF/classes BUILD FAILED /home/faith/treeDev/build.xml:118: Cannot use classic compiler, as it is not available ---------------------------------- Stefan Bodewig wrote: > Joe Faith wrote: > > > I keep getting the error message > > > > Cannot use classic compiler, as it is not available > > > > when trying to compile Java classes with ant. > > Javac works fine from the (Debian Linux) command line. > > > > I've checked that PATH includes javac, and that CLASSPATH includes > > tools.jar. > > Usually it is the missing tools.jar, but as you've already checked > this ... > > Put the following right in front of your javac task: > > > > This will give you the CLASSPATH Ant has been invoked with. See if > tools.jar is there and no typo occurred. > > The easiest way to ensure that Ant will pick up tools.jar is setting > JAVA_HOME correctly and invoke Ant via its ant shell script BTW, no > need to put tools.jar in your CLASSPATH manually. > > Stefan -- Joe Faith Runtime Collective --------------41AA2ABD05095B457217E859 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Stefan,

all present and correct.
Yours, still baffled

Joe

--------------------------------
ant
Searching for build.xml ...
Buildfile: /home/faith/treeDev/build.xml

prepare:

compile:
/home/java/jakarta-ant/lib/ant.jar:/home/java/jakarta-ant/lib/jaxp.jar:/home/java/jakarta-ant/lib/parser.jar:/home/java/jdk1.2.2/lib/tools.jar
    [javac] Compiling 4 source files to /home/faith/treeDev/tomcat/webapps/tree/WEB-INF/classes

BUILD FAILED

/home/faith/treeDev/build.xml:118: Cannot use classic compiler, as it is not available
----------------------------------
 

Stefan Bodewig wrote:

Joe Faith <faith@runtime-collective.com> wrote:

> I keep getting the error message
>
>     Cannot use classic compiler, as it is not available
>
> when trying to compile Java classes with ant.
> Javac works fine from the (Debian Linux) command line.
>
> I've checked that PATH includes javac, and that CLASSPATH includes
> tools.jar.

Usually it is the missing tools.jar, but as you've already checked
this ...

Put the following right in front of your javac task:

<echo message="${java.class.path}" />

This will give you the CLASSPATH Ant has been invoked with. See if
tools.jar is there and no typo occurred.

The easiest way to ensure that Ant will pick up tools.jar is setting
JAVA_HOME correctly and invoke Ant via its ant shell script BTW, no
need to put tools.jar in your CLASSPATH manually.

Stefan


--

Joe Faith
Runtime Collective
  --------------41AA2ABD05095B457217E859--