sp00m sp00m - 7 months ago 28
Java Question

How to see the compiler output when running javac through an Ant task?

Is there any clearly explained and simple way to see the compiler output when running

through an Ant task?

Here is my
Ant tag:

<javac srcdir="${myproject.src}" destdir="${myproject.class}">
<!-- ... -->

Here is the only error message I get:

/path/to/build.xml:42: Compile failed; see the compiler error output for details.

The problem is that I don't know how to see the compiler error output for details...

Few configuration elements that may help:

  • Ant 1.6.5

  • Windows 7 x64

  • Java 1.6.0_20 x32

  • Launching targets via Eclipse

I know there are some related answered questions on SO, but none of them really answers this simple questions:


I think you're looking for the verbose="true" attribute.

Asks the compiler for verbose output; defaults to no.

You already mentioned in the comments that this doesn't print the cause of your error. Well I think something else is going on in your situation. I have a sample project and either way the cause of my error was printed. Here's the output with verbose="false":

[mkdir] Created dir: C:\Projects\MavenSandbox\target\classes
[javac] C:\Projects\MavenSandbox\mavensandbox.xml:284: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 3 source files to C:\Projects\MavenSandbox\target\classes
[javac] C:\Projects\MavenSandbox\src\main\java\com\sandbox\Sandbox.java:8: error: cannot find symbol
[javac]         System.out.prinln("Hello, I\'m the best!");
[javac]                   ^
[javac]   symbol:   method prinln(String)
[javac]   location: variable out of type PrintStream
[javac] 1 error

Something strange and specific to your code is causing the bad error message. Can you create a sample project that reproduces the error?

As you mentioned, debug="true" is not the attribute you're looking for.

Indicates whether source should be compiled with debug information; defaults to off. If set to off, -g:none will be passed on the command line for compilers that support it (for other compilers, no command line argument will be used). If set to true, the value of the debuglevel attribute determines the command line argument.

You know when you get stack trace and it has line numbers in it? That's what debug="true" does. If it's off, you don't get line numbers.