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 4189] - Command line too long on NT during ejbc task
Date Tue, 16 Oct 2001 15:40:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4189>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4189

Command line too long on NT during ejbc task





------- Additional Comments From reg.whitton@ifonline.com  2001-10-16 08:40 -------
Have tried this again in 1.4.1 and the problem is still the same.

The problem is (as suspected) the use of cmd.exe which must have a limited 
command line.  I changed a copy of org.apache.tools.ant.taskdefs.Execute so 
that the method WinNTCommandLauncher does not piggy back the command on cmd.exe 
and so does not change directory.  This works fine for me as I always run Ant 
in my project directory.

There appears to be no other way to change the current working directory for 
the sub-process in java (why is that?). So there doesn't seem to be a easy 
generic solution to this problem.

Maybe there it could be done with a native executable for piggy backing 
commands (like env except it changes dir instead of the environment).

Mime
View raw message