You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by "Petar Tahchiev (JIRA)" <ca...@jakarta.apache.org> on 2008/04/11 14:42:05 UTC
[jira] Updated: (CACTUS-236) CLONE -It's not possible to set a
timeout for the containers
[ https://issues.apache.org/jira/browse/CACTUS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petar Tahchiev updated CACTUS-236:
----------------------------------
Fix Version/s: (was: 1.8)
> CLONE -It's not possible to set a timeout for the containers
> ------------------------------------------------------------
>
> Key: CACTUS-236
> URL: https://issues.apache.org/jira/browse/CACTUS-236
> Project: Cactus
> Issue Type: Improvement
> Components: Maven Integration
> Affects 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org