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 2005/10/19 15:43:44 UTC
[jira] Created: (CACTUS-231) It's not possible to set a timeout for the containers
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
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] Commented: (CACTUS-231) 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-231?page=comments#action_12332484 ]
Felipe Leme commented on CACTUS-231:
------------------------------------
Ok, so let's add the containerset property for the current plugin (with is on the 1.7 BRANCH) and then the individual settings for the Cargo-based plugin (which is on HEAD); to keep compatibility, the individual values could receive the value of the containerset property.
> 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
[jira] Closed: (CACTUS-231) 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-231?page=all ]
Felipe Leme closed CACTUS-231:
------------------------------
Fix Version: 1.7.2
Resolution: Fixed
Marking as fixed, as I have opened a close (CACTUS-236) for 1.8...
> 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
> Fix For: 1.7.2
>
> 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] Commented: (CACTUS-231) 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-231?page=comments#action_12332719 ]
Felipe Leme commented on CACTUS-231:
------------------------------------
Fixed on the 1.7 branch; will do it on main/cargo later...
> 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
[jira] Commented: (CACTUS-231) It's not possible to set a timeout for the containers
Posted by "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