[
http://jira.codehaus.org/browse/CARGO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189593#action_189593 ]
Matt Wringe commented on CARGO-707:
-----------------------------------
The wait behaviour is acting in the way it was intended.
Cargo is usually used for testing, and we don't necessarily want the server to be running after a test has been completed.
Having the server use a separate VM instance and remain running after the maven task has been completed might be a good option.
Maybe have a <persist>true<persist> option? This could then just add the spawn = true option to the internal ant java tasks.
Any other thoughts on this?
> <wait>false</wait> is not possible for InstalledLocalContainer or ExistingLocalContainer Jboss5x
> ------------------------------------------------------------------------------------------------
>
> Key: CARGO-707
> URL:
http://jira.codehaus.org/browse/CARGO-707> Project: Cargo
> Issue Type: Bug
> Components: JBoss
> Affects Versions: 1.0
> Reporter: Robert Herschke
> Priority: Critical
>
> The option <wait>false</wait> does not work correct for jboss5x.
> After the server is started and maven finishes, the VM is disposed and therefor the jboss is also droped.
> Please start jboss in another VM then the maven VM, so that it remains started after maven finished.
--
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
