ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46305] Hung forked JVM when reading from standard input
Date Fri, 24 Sep 2010 18:15:00 GMT

--- Comment #5 from flushdia <> 2010-09-24 14:14:56 EDT ---
I am experiencing similar issues when using forked <java> followed by <input>.
Let me explain the details.

Consider the following snippet of Ant XML code:

  <target name="java-input">
    <java classname="" fork="true">
        <pathelement location="${ant.home}/lib/ant-launcher.jar" />
      <arg value="-buildfile" />
      <arg file="echo.xml" />
      <arg value="echo" />
    <input message="Do you want to proceed" validargs="y,n" defaultvalue="y"
addproperty="proceed" />
    <echo>User selected [${proceed}]</echo>

When running this target, <input> asks for input two times (not one) and
accepts second entry as actual input.

Issue is not reproduced when running with fork="true" and spawn="true" OR with

Issue can be fixed by adding inputstring="" to <java>, but what if <java> has
to accept some input as well?

Shouldn't Ant workaround such situation?

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

View raw message