[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Matt Hogstrom updated GERONIMO-803:
-----------------------------------
Fix Version: 1.1
(was: 1.0)
Moving to 1.1
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Fix For: 1.1
>
> Ouch, this is a nasty one. If you deploy app Foo, then change it to be
> broken (invalid DD, whatever) and redeploy it, it goes like this:
> 1) undeploy old one
> 2) try to deploy new one
> 3) fail
> The result is that the old one has been undeployed but the new one hasn't
> been deployed. It would be ideal if we could "try" the deploy operation
> first, and only if it appears valid, undeploy the old version and start the
> new version. I'm not sure how that could be done.
--
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
