geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2025) Undeploy and redeploy with no version leaves dangling entries in config.xml
Date Thu, 11 Oct 2007 03:41:50 GMT


Kevan Miller updated GERONIMO-2025:

    Fix Version/s:     (was: 2.0.2)

Moving out of 2.0.2 to 2.0.x. Has anyone tested this behavior to see if it is still an issue?

> Undeploy and redeploy with no version leaves dangling entries in config.xml
> ---------------------------------------------------------------------------
>                 Key: GERONIMO-2025
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, kernel
>    Affects Versions: 1.1, 2.0.x, 2.1
>            Reporter: Aaron Mulder
>            Assignee: Rakesh Midha
>             Fix For: 2.0.x, 2.1
>         Attachments: removeunwantedconfig.patch
> If you deploy an application with no version and then undeploy it, we leave an entry
for it (with a timestamp version number) in config.xml, just marked as load=false.
> If you later deploy the application again, you get a new timestamp version number and
a new entry is written into config.xml.  Do this (undeploy/deploy) a few times and config.xml
gets kind of messy.
> It would be be good to delete entries from config.xml on undeploy if they have no actual
> It would be good to detect that a previous version is in conifg.xml but not in the repository
and delete the settings from config.xml if the artifact has no version number and a newer
copy is deployed.
> This is not a huge priority since nothing breaks, it just makes config.xml kind of crufty.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message