ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34461] problems with core <java fork="true"> task
Date Fri, 28 May 2010 18:49:46 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=34461

--- Comment #21 from troy.harris@sas.com 2010-05-28 14:49:33 EDT ---
The FAQ entry states that this can be a problem with <exec> tasks as well.  I
am looking at the source for ant 1.7.0 and I can see the change that was made
for Bug #24918 in the source for the <java> task.  It appears that I just need
to comment out the following code in Java.java to remove the change:

/*
if (!spawn && input == null && inputString == null) {
     // #24918: send standard input to the process by default.
     redirector.setInputStream(
     new KeepAliveInputStream(getProject().getDefaultInputStream()));
}
*/

Is the only change required to remove the functionality provided by Bug #24918?

I don't see any such code in ExecTask.java, but the FAQ entry for the hang on
StandradInput says this:

"When Ant forks a new process for example by using the <exec>, <apply> or
<java> tasks, it will also start a new thread reading from standard input and
sending everything that it has read to that process."

What else is required to build 1.7.0 without the fixes to hookup standard in on
these tasks?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Mime
View raw message