ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Faith <fa...@runtime-collective.com>
Subject Re: Cannot use classic compiler, as it is not available
Date Thu, 30 Nov 2000 16:09:21 GMT
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


Mime
View raw message