You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org> on 2006/07/16 09:07:00 UTC
[jira] Updated: (GERONIMO-1431) Make deploy tool and hot deploy
directory work better together
[ http://issues.apache.org/jira/browse/GERONIMO-1431?page=all ]
Alan Cabrera updated GERONIMO-1431:
-----------------------------------
Fix Version/s: 1.1.x
(was: 1.1.1)
Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch.
> Make deploy tool and hot deploy directory work better together
> --------------------------------------------------------------
>
> Key: GERONIMO-1431
> URL: http://issues.apache.org/jira/browse/GERONIMO-1431
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment, Hot Deploy Dir
> Affects Versions: 1.0
> Reporter: Aaron Mulder
> Priority: Critical
> Fix For: 1.1.x
>
>
> Right now if you deploy something with the deploy tool and then drop an update in the hot deploy directory, it doesn't work. The hot deploy dir expects you to only use the hot dpeloy dir for that module.
> Likewise, if you deploy something with the hot deploy dir and then undeploy it with the deploy tool, it is not deleted from the hot deploy dir.
> Both of those can be fixed.
--
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