ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy-Lambert <anto...@antbuild.com>
Subject AW: AW: AW: two diff't JDKs
Date Tue, 28 Oct 2003 09:20:39 GMT
Hi Erik,
I think that you need to use both the compiler !!!and!!! the executable
attributes of <javac> in order to be able to compile properly with javac
1.1.
The problem that you are experiencing is that ant is sending command line
arguments to javac 1.1 in the 1.2 format which javac 1.1 does not
understand.
So do <javac executable="c:/jdk1.1/bin/javac.exe" compiler="classic" ...>
and it should work fine for you.
The executable attribute tells ant where physically the compiler lives.
The compiler attribute tells ant how to talk to the compiler.

Cheers,
Antoine

-----Ursprungliche Nachricht-----
Von: Erik Price [mailto:profkyne@yahoo.com]
Gesendet: Dienstag, 28. Oktober 2003 01:07
An: Ant Users List
Betreff: RE: AW: AW: two diff't JDKs



--- Erik Price <profkyne@yahoo.com> wrote:

> Mike,
>
> An unescaped space was my first guess, too -- it looks almost as
> though
> the command that Ant is executing to the DOS shell isn't well-formed
> somehow.  It would seem most likely that the unescaped space is in
> one
> of my arguments, as you suggest, but if so then I just can't find it
> anywhere.  When I run Ant in -verbose mode so that I can see exactly
> what is happening, I find the following amidst numerous warnings
> about
> using C:\com\foo instead of C:/com/foo:
>
>     [javac] Compiling 1336 source files to
> C:\newdist\mswp-2a\build\classes
>     [javac] Using external javac compiler
>     [javac] Compilation arguments:
>     [javac] '-d'
>     [javac] 'C:\newdist\mswp-2a\build\classes'
>     [javac] '-classpath'
>     [javac]
>
'C:\newdist\mswp-2a\build\classes;C:\newdist\mswp-2a\lib\borland.jar;C:\newd
ist\mswp-2a\lib\classes12.zip;C:\newdist\mswp-2a\lib\jaxp.jar;C:\newdist\msw
p-2a\lib\junit.jar;C:\newdist\mswp-2a\lib\parser.jar;C:\newdist\mswp-2a\lib\
rmiStub_Skel.jar;C:\newdist\mswp-2a\lib\servlet.jar;C:\newdist\mswp-2a\lib\s
wingall.jar;C:\newdist\mswp-2a\lib\vbjapp.jar;C:\newdist\mswp-2a\lib\vbjcose
v.jar;C:\newdist\mswp-2a\lib\vbjcosnm.jar;C:\newdist\mswp-2a\lib\vbjgk.jar;C
:\newdist\mswp-2a\lib\vbjorb.jar;C:\newdist\mswp-2a\lib\vbjtools.jar;C:\newd
ist\mswp-2a\lib\xml4j_1_1_9.jar;C:\newdist\tools\jdk\1.3.0_02\lib\tools.jar;
C:\code\apache-ant-1.5.4\lib\xml-apis.jar;C:\code\apache-ant-1.5.4\lib\xerce
sImpl.jar;C:\code\apache-ant-1.5.4\lib\optional.jar;C:\code\apache-ant-1.5.4
\lib\ant.jar'
>     [javac] '-g:none'
>     [javac]
>     [javac] The ' characters around the executable and arguments are
>     [javac] not part of the command.
>
> And then it lists all of the files it's about to compile, at which
> point it gets to the very end and then ends with the "-g:none"
> argument
> error.

Is there any possibility that there is a problem when the file is
constructed of the form "@C:\filename\fileRANDNUMBER"?

This gets created in Java13CommandLauncher.exec() (from
Execute.executeExternalCompile()).

Thanks!

ERik



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message