geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Resolved: (GERONIMO-1940) Bad deployment can't be undeployed
Date Thu, 04 May 2006 18:04:18 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1940?page=all ]
     
Aaron Mulder resolved GERONIMO-1940:
------------------------------------

    Resolution: Fixed

> Bad deployment can't be undeployed
> ----------------------------------
>
>          Key: GERONIMO-1940
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1940
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: db-plan-no-deps.xml
>
> If you deploy something that can't start, so it ends up in a not-started-but-not-stopped
state (failed? starting?) then you can't stop or undeploy it and you're kind of stuck.  For
example, try deploying the attached database plan.

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


Mime
View raw message