You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Jing Xue <vi...@manifoldronin.com> on 2003/12/05 22:48:20 UTC
'compiler' and 'fork' ignores each other
The document for <javac> states:
"The fork attribute overrides the build.compiler property or compiler attribute
setting and expects a JDK1.1 or higher to be set in JAVA_HOME."
But when I run:
<javac srcdir="src" destdir="classes" debug="${javac.debug}"
deprecation="${javac.deprecation}" source="1.4"
fork="yes" executable="${env.JAVA_HOME}/bin/javac.exe">
<classpath>
<path refid="project.classpath"/>
</classpath>
</javac>
I get:
[javac] Since compiler setting isn't classic or modern,ignoring fork setting.
Then when I try:
<javac srcdir="src" destdir="classes" debug="${javac.debug}"
deprecation="${javac.deprecation}" source="1.4"
compiler="modern" fork="yes" executable="${env.JAVA_HOME}/bin/javac.exe">
<classpath>
<path refid="project.classpath"/>
</classpath>
</javac>
I get:
[javac] Since fork is true, ignoring compiler setting.
--J.X.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: 'compiler' and 'fork' ignores each other
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 9 Dec 2003, Jing Xue <vi...@manifoldronin.com> wrote:
> Quoting Stefan Bodewig <bo...@apache.org>:
>> Oops, build.compiler was what I meant.
>
> I don't have that explicitly specified either.
Could you please echo it, even if you don't consciously set it?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: 'compiler' and 'fork' ignores each other
Posted by Jing Xue <vi...@manifoldronin.com>.
Quoting Stefan Bodewig <bo...@apache.org>:
> On Mon, 8 Dec 2003, J. Xue <an...@manifoldronin.com> wrote:
> > That's the point, I do *not* have any compiler setting in the
> > script. It seems to be checking some default value of the
> > 'compiler' attribute.
>
> The defaults are either modern or classic, depending on your VM.
Right, but that's exactly the point I'm trying to make here (or the one I'm
missing) 8-) If I do *not* specify a 'compiler' attribute, while I do have
a 'fork' attribute, 'fork' obviously should take precedence. However in my
example, 'fork' is ignored because of some default value of the 'compiler'
attribute I have never specified.
> Oops, build.compiler was what I meant.
I don't have that explicitly specified either.
--J.X.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: 'compiler' and 'fork' ignores each other
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 8 Dec 2003, J. Xue <an...@manifoldronin.com> wrote:
> Quoting Stefan Bodewig <bo...@apache.org>:
>> I don't see any compiler setting here.
>
> That's the point, I do *not* have any compiler setting in the
> script. It seems to be checking some default value of the
> 'compiler' attribute.
The defaults are either modern or classic, depending on your VM.
>> build.sysclasspath?
>
> I have never set build.sysclasspath (not consciously, at least).
Oops, build.compiler was what I meant.
Stefan
--
http://stefanbodewig.blogger.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: 'compiler' and 'fork' ignores each other
Posted by "J. Xue" <an...@manifoldronin.com>.
Quoting Stefan Bodewig <bo...@apache.org>:
> On Fri, 5 Dec 2003, Jing Xue <vi...@manifoldronin.com> wrote:
>
> > when I run:
> > <javac srcdir="src" destdir="classes" debug="${javac.debug}"
> > deprecation="${javac.deprecation}" source="1.4"
> > fork="yes" executable="${env.JAVA_HOME}/bin/javac.exe">
> > <classpath>
> > <path refid="project.classpath"/>
> > </classpath>
> > </javac>
> >
> > I get:
> > [javac] Since compiler setting isn't classic or modern,ignoring
> > fork setting.
>
> I don't see any compiler setting here. What's the value of
That's the point, I do *not* have any compiler setting in the script. It seems
to be checking some default value of the 'compiler' attribute.
> build.sysclasspath?
I have never set build.sysclasspath (not consciously, at least).
BTW, I'm using Ant 1.6 Beta 3.
Thanks.
--J.X.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: 'compiler' and 'fork' ignores each other
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 5 Dec 2003, Jing Xue <vi...@manifoldronin.com> wrote:
> when I run:
> <javac srcdir="src" destdir="classes" debug="${javac.debug}"
> deprecation="${javac.deprecation}" source="1.4"
> fork="yes" executable="${env.JAVA_HOME}/bin/javac.exe">
> <classpath>
> <path refid="project.classpath"/>
> </classpath>
> </javac>
>
> I get:
> [javac] Since compiler setting isn't classic or modern,ignoring
> fork setting.
I don't see any compiler setting here. What's the value of
build.sysclasspath?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org