geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <>
Subject [jira] Closed: (GERONIMO-2437) Empty dirs and config.xml entries left behind after undeploy
Date Wed, 13 Dec 2006 17:00:21 GMT
     [ ]

Vamsavardhana Reddy closed GERONIMO-2437.

    Resolution: Fixed

Fixed in rev 486734 in branches\1.1, branches\1.2, branches\2.0-M1 and trunk.

 o Removes the uninstalled configurations from PersistentConfigurationList
 o Checks for parent directories upto 3 levels and deletes empty directories
 o FIXME: Repository is assumed to be Maven2Repository (thus checking 3 levels up).  May need
a mechanism to determine the repository type and the number of directory levels to check for
empty dirs. 

> Empty dirs and config.xml entries left behind after undeploy
> ------------------------------------------------------------
>                 Key: GERONIMO-2437
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1.x, 1.2
>            Reporter: Prasad Kashyap
>         Assigned To: Vamsavardhana Reddy
>             Fix For: 1.1.2, 1.2, 2.0-M1
> After an undeploy, it's entry is left behind in the config.xml with a "load=false"
> In the repository, the groupid/artifactid/version directory is left behind, empty however.
> I am not sure if this is a regression from 1.1.

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