ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nisha Pillai <>
Subject Re: -J option <javac> task question
Date Fri, 02 May 2003 19:38:24 GMT
Stefan Bodewig wrote:

>On Wed, 30 Apr 2003, Nisha Pillai <> wrote:
>> Realized when I saw ANT_OPTS working that fork wasn't working, but
>> I'm not sure why. Anyone?
>Can you give us the complete javac related part of ant -debug?
>Ant is going to tell us which compiler adapter it uses (and with a
>little luck it will also tell us why).
   Here it is :   
<listing of 722 files during creation of the fileset> followed by
[javac] Compiling 722 source files to E:\CVS\FCSRelease\Vivaldi\classes
    [javac] Using modern compiler
fileset: Setup scanner in dir E:\CVS\FCSRelease\Vivaldi\external_jars 
with patternSet{ includes: [**/*.jar] excludes: [] }
    [javac] Compilation arguments:
    [javac] '-d'
    [javac] 'E:\CVS\FCSRelease\Vivaldi\classes'
    [javac] '-classpath'
    [javac] '-sourcepath'
    [javac] 'E:\CVS\FCSRelease\Vivaldi\src'
    [javac] '-g'
followed by <list of files being compiled - 722 filenames with full path 
to each>

Just for completeness, here is the target definition :
<target name="compile" depends="init" description="compile the source " >
   <!-- Compile the java code from ${src} into ${build} -->
   <javac srcdir="${src}" destdir="${build}" debug="on" fork="yes" 
     <fileset dir="${maindir}/external_jars" includes="**/*.jar"/>
     <pathelement path="${java.class.path}/"/>

- Nisha.

View raw message