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 4092] New: - <Exec /> does not give the control back to ant
Date Thu, 11 Oct 2001 09:09:31 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=4092>.
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=4092

<Exec /> does not give the control back to ant

           Summary: <Exec /> does not give the control back to ant
           Product: Ant
           Version: 1.4
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: sascha.ehrkamp@pixelpark.com


If you try to start a blocking command (e.g. starting tomcat) with the <exec/> 
task, ant will not continue execution until the command has finished.

Also a command like this:
exec executable="cmd" dir="${tomcat.dir}/bin" os="Windows NT">
  <arg line=" /c startup.cmd" />
</exec>
doesn't fix the problem.

If you use a "start" command instead of "cmd" there is no change.

We even tried to use "start" in the "startup.cmd":
A window will popup starting another window and showing the cmd-Shell.
If you exit the cmd with exit, the first window closes, and the command (e.g. 
tomcat) is running in the second window.
But even in this case ant does not get the control back. It blocks!

Mime
View raw message