[
https://jira.codehaus.org/browse/CARGO-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eduardo Horai updated CARGO-364:
--------------------------------
Attachment: CARGO-364 Spawn.patch
Can you have a look at this implementation?
Basically, if the property "cargo.process.spawn" is true, then a flag is set in the JvmLauncher to start the Ant Java task in spawn mode.
JvmLauncher and AntContainerExecutorThread has to keep that flag to avoid "fail on exception" which is not supported by the Ant Java Task if spawn is true.
> Ant task/Maven2 plugin should use the spawn option on exec/java to enable the app server to outlive ant
> -------------------------------------------------------------------------------------------------------
>
> Key: CARGO-364
> URL:
https://jira.codehaus.org/browse/CARGO-364> Project: Cargo
> Issue Type: Improvement
> Components: Ant, Maven2
> Affects Versions: 0.8
> Environment: Java1.5, ant1.7alpha., winxp SP2, ethernet.
> Reporter: Steve Loughran
> Fix For: 1.3.0
>
> Attachments: CARGO-364 Spawn.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
