[jira] Commented: (CACTUS-231) It's not possible to set a timeout for the containers

["Vincent Massol (JIRA)" <ca...@jakarta.apache.org>]

    [ http://issues.apache.org/jira/browse/CACTUS-231?page=comments#action_12332483 ] 

Vincent Massol commented on CACTUS-231:
---------------------------------------

Cargo does allow the timeout to be set individually. Actually Cargo has no notion of containerset at all ATM (there's been no use case requiring it yet).

> It's not possible to set a timeout for the containers
> -----------------------------------------------------
>
>          Key: CACTUS-231
>          URL: http://issues.apache.org/jira/browse/CACTUS-231
>      Project: Cactus
>         Type: Improvement
>   Components: Maven Integration
>     Versions: 1.7.1
>     Reporter: Felipe Leme
>     Assignee: Felipe Leme

>
> The <containerset> Ant task has an optional timeout attribute, but the Maven plugin does not offer an option for the user to set such an attribute.
> For the current plugin, it would be enough to just create one property (such as cactus.containerset.timeout), as this value must be passed to the set, not for each individual container. But what about the Cargo version? Does cargo allows such parameter to be set individually?
> -- Felipe

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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