geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Updated: (GERONIMO-803) Deploy failure during redeploy leaves app undeployed
Date Wed, 26 Apr 2006 21:42:03 GMT
     [ ]

Aaron Mulder updated GERONIMO-803:

    Fix Version: 1.1
                     (was: 1.2)
       Priority: Critical  (was: Major)

Should be fixed, just need to test.

> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>          Key: GERONIMO-803
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Critical
>      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:
For more information on JIRA, see:

View raw message