ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 50781] javac task creates long command line
Date Tue, 22 May 2012 18:18:52 GMT

--- Comment #7 from Jesse Glick <> ---
Jikes's home page has not been updated in seven years, and jvc is ancient
history. We should optimize for the problem affecting users of current tools;
@args works for me with javac 1.4.2b19 and later (*), and also with ecj 3.5.1.
And remember that you can use a current javac and pass -source 1.2
-bootclasspath ... to build for an old platform without actually using a
compiler binary from the previous millenium.

If there is a way to automatically detect that an obsolete compiler is in use,
great, but I am not sure what that would be, especially if it is just known
that C:\something\bin\javac.exe is to be invoked. If we need to retain
compatibility here, we should default to the behavior in the patch, but make it
possible to restore the prior behavior using a project property (or, if
necessary, task attribute).

(In reply to comment #5)
> This code only runs if the
> command line is too long, which means they've had this error for ages

My understanding is that if you are compiling a large number of source files
with a short classpath using a very old compiler, the 1.8.3 task will work but
the task with the proposed patch will fail.

(*) JDK 1.3 can no longer be made to run on Linux without great effort.

You are receiving this mail because:
You are the assignee for the bug.

View raw message