You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2007/09/21 17:19:50 UTC
[jira] Created: (GERONIMO-3483) Redeploy should start any dependent
configurations it stops.
Redeploy should start any dependent configurations it stops.
------------------------------------------------------------
Key: GERONIMO-3483
URL: https://issues.apache.org/jira/browse/GERONIMO-3483
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 2.0.1, 2.0.x, 2.1
Reporter: Vamsavardhana Reddy
Fix For: 2.0.x, 2.1
When a configuration is redeployed, any dependent configurations stopped are not automatically restarted after redeploy step. The user will have to manually start the stopped configs. It will be useful if the deployer starts all the configurations it stopped during redeploy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3483) Redeploy should start any dependent
configurations it stops.
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-3483:
-----------------------------------
Fix Version/s: (was: 2.2)
Wish List
This might not be too hard since IIUC the plugin installer does this but this is not happening for 2.2
> Redeploy should start any dependent configurations it stops.
> ------------------------------------------------------------
>
> Key: GERONIMO-3483
> URL: https://issues.apache.org/jira/browse/GERONIMO-3483
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0.1, 2.0.x, 2.1, 2.1.1
> Reporter: Vamsavardhana Reddy
> Fix For: Wish List
>
>
> When a configuration is redeployed, any dependent configurations stopped are not automatically restarted after redeploy step. The user will have to manually start the stopped configs. It will be useful if the deployer starts all the configurations it stopped during redeploy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3483) Redeploy should start any dependent
configurations it stops.
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn updated GERONIMO-3483:
-------------------------------
Fix Version/s: (was: 2.1.1)
(was: 2.0.x)
2.2
> Redeploy should start any dependent configurations it stops.
> ------------------------------------------------------------
>
> Key: GERONIMO-3483
> URL: https://issues.apache.org/jira/browse/GERONIMO-3483
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0.1, 2.0.x, 2.1, 2.1.1
> Reporter: Vamsavardhana Reddy
> Fix For: 2.2
>
>
> When a configuration is redeployed, any dependent configurations stopped are not automatically restarted after redeploy step. The user will have to manually start the stopped configs. It will be useful if the deployer starts all the configurations it stopped during redeploy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3483) Redeploy should start any dependent
configurations it stops.
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller updated GERONIMO-3483:
-----------------------------------
Affects Version/s: 2.1.1
Fix Version/s: (was: 2.1)
2.1.1
Anybody have a test case for this? Moving to 2.1.1
> Redeploy should start any dependent configurations it stops.
> ------------------------------------------------------------
>
> Key: GERONIMO-3483
> URL: https://issues.apache.org/jira/browse/GERONIMO-3483
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0.1, 2.0.x, 2.1, 2.1.1
> Reporter: Vamsavardhana Reddy
> Fix For: 2.0.x, 2.1.1
>
>
> When a configuration is redeployed, any dependent configurations stopped are not automatically restarted after redeploy step. The user will have to manually start the stopped configs. It will be useful if the deployer starts all the configurations it stopped during redeploy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.