You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org> on 2006/04/06 21:01:39 UTC

[jira] Updated: (GERONIMO-1483) During Undeploy entry in config.xml is not removed

     [ http://issues.apache.org/jira/browse/GERONIMO-1483?page=all ]

Dain Sundstrom updated GERONIMO-1483:
-------------------------------------

    Component: console
               deployment

> During Undeploy entry in config.xml is not removed
> --------------------------------------------------
>
>          Key: GERONIMO-1483
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1483
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console, deployment
>  Environment: WinXP, JDK1.4.2_09 X86 Intel
>     Reporter: Manu T George
>     Assignee: Aaron Mulder
>     Priority: Minor

>
> Suppose I have two modules A and B and A is dependant  on B. Usually we first remove A and then  B . This works fine. If we remove B and then A then the entry in config.xml is not removed and the server does not allow me to again deploy the module A. This problem was noticed on running the deploy command. from console

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