[
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.
