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 "Felipe Leme (JIRA)" <ca...@jakarta.apache.org> on 2006/01/15 02:05:19 UTC
[jira] Created: (CACTUS-236) CLONE -It's not possible to set a
timeout for the containers
CLONE -It's not possible to set a timeout for the containers
------------------------------------------------------------
Key: CACTUS-236
URL: http://issues.apache.org/jira/browse/CACTUS-236
Project: Cactus
Type: Improvement
Components: Maven Integration
Versions: 1.7.1
Reporter: Felipe Leme
Assigned to: 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
[jira] Updated: (CACTUS-236) CLONE -It's not possible to set a
timeout for the containers
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/CACTUS-236?page=all ]
Felipe Leme updated CACTUS-236:
-------------------------------
Fix Version: 1.8
I cloned this issue, so CACTUS-231 is marked as closed (as it has been added to cactus 1.7.2)...
> CLONE -It's not possible to set a timeout for the containers
> ------------------------------------------------------------
>
> Key: CACTUS-236
> URL: http://issues.apache.org/jira/browse/CACTUS-236
> Project: Cactus
> Type: Improvement
> Components: Maven Integration
> Versions: 1.7.1
> Reporter: Felipe Leme
> Assignee: Felipe Leme
> Fix For: 1.8
>
> 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
[jira] Updated: (CACTUS-236) CLONE -It's not possible to set a
timeout for the containers
Posted by "Petar Tahchiev (JIRA)" <ca...@jakarta.apache.org>.
[ 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