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=17880>. 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=17880 <java> task should optionally not destroy forked processes Summary: <java> task should optionally not destroy forked processes Product: Ant Version: 1.5.2 Platform: Other OS/Version: Linux Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] A feature in Ant 1.4 was that a forked Java process would continue after the Ant VM has terminated. This was useful as it allowed you to write a task to, say, start Tomcat. This feature was lost in the move to 1.5.x. The attachments restore this feature as an option. They update the 1.5.2beta1 source to give the <java> task a "destroy" option which defaults to True, which is the current 1.5.x behaviour. Switching this to False means forked process continues after the Ant VM, giving 1.4 behaviour. More comments are contained in the attached source. Updated documentation is also attached.
