ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32012] - JavaC task seems to produce invalid switches to javac command
Date Tue, 02 Nov 2004 15:33:19 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32012>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32012

JavaC task seems to produce invalid switches to javac command





------- Additional Comments From stevel@apache.org  2004-11-02 15:33 -------
This is interesting. 

First -J-Xmx256m is legit for the current javac. From the docs

"-Joption
    Pass option to the java launcher called by javac. For example, -J-Xms48m
sets the startup memory to 48 megabytes. Although it does not begin with -X, it
is not a `standard option' of javac. It is a common convention for -J to pass
options to the underlying VM executing applications written in Java."


So if your version of Javac is unhappy, we have something very unusual indeed.
Nothing obvious springs to mind; I've never encountered this before. The only
javac implementations i'd expect trouble on is the MS jvc.exe, and that doesnt
count. 

1. you may want to try jikes instead. Its faster; you'll love it.

2. set fork=false to get the in-JVM javac; for which you may need to tune memory
requirements of ant itself, if you really need 256M.

3. what is the output of running the target in -verbose mode?

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


Mime
View raw message