[
http://jira.codehaus.org/browse/CARGO-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Savas Ali Tokmen closed CARGO-364.
----------------------------------
Resolution: Won't Fix
That's actually the way CARGO works: CARGO has not been designed for launching and leaving alone containers but rather launch a container, for example deploy applications to run tests and stop in the same project.
I guess trying to do something against would be a bad idea (for now).
> Ant task should use the spawn option on exec/java to enable the app server to outlive ant
> -----------------------------------------------------------------------------------------
>
> Key: CARGO-364
> URL:
http://jira.codehaus.org/browse/CARGO-364> Project: Cargo
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8
> Environment: Java1.5, ant1.7alpha., winxp SP2, ethernet.
> Reporter: Steve Loughran
>
> Since Java1.5, the exec and java tasks have had a spawn option, that ensures that an application will outlive the ant run. It's pretty brutal how it is done, as there is no way to chain up the output channel of the spawned process and have it outlive ant.
> if the <cargo> task somehow exposed the spawn option, cargo could be used to launch the app server, so ant itself could act as a launcher script.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
