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 30631] - Need a way to get process-id for <exec..> task
Date Fri, 13 Aug 2004 09:10:50 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30631>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30631

Need a way to get process-id for <exec..> task

stevel@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From stevel@apache.org  2004-08-13 09:10 -------
you have to remember that Ant is a build tool, not a generic
process-execution-workflow language. It often gets used as the latter, but it is
not its strength. 

futhermore, there is no notion of processID in java processes; that is an
OS-specific abstraction that is hidden from us unworthy developers :) So we
cannot get a process ID, or implement a kill in a cross platform manner.

Can I point you at the smartfrog deployment framework ( http://smartfrog.org/ )
which is designed to manage long running processes with secure remote
deploy/undeploy/health checks. There is a new release due by the end of the
month, with ant tasks included. It avoids the processID problem by having a
daemon running continually to remember what was deployed, the same program that
responds to local/remote deploy/undeploy requests.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message