geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Man <man.geron...@gmail.com>
Subject Re: [jira] Updated: (GERONIMO-1431) Make deploy tool and hot deploy directory work better together
Date Fri, 28 Apr 2006 10:32:03 GMT
I had sumitted a patch , that address a similar issue. Infact i
remember Aaron adviced me to submit the patch for this.

Actual Issue : If a application module is already deployed , and somebody
tries to hot deploy , the same application , server use to throw an error
and still keep the module in hot deploy directory .

Patch : The patch was for deleting the application module from hot deploy
directory for above issue . Probably I think , this is what in real scenario
the server has to do.

Tha patch is available with JIRA 1813

With thanks,
Mansoor




On 4/27/06, Aaron Mulder (JIRA) <dev@geronimo.apache.org> wrote:
>
>     [ http://issues.apache.org/jira/browse/GERONIMO-1431?page=all ]
>
> Aaron Mulder updated GERONIMO-1431:
> -----------------------------------
>
>    Fix Version: 1.1
>                     (was: 1.2)
>      Assign To: Aaron Mulder
>       Priority: Critical  (was: Major)
>
> > Make deploy tool and hot deploy directory work better together
> > --------------------------------------------------------------
> >
> >          Key: GERONIMO-1431
> >          URL: http://issues.apache.org/jira/browse/GERONIMO-1431
> >      Project: Geronimo
> >         Type: Improvement
> >     Security: public(Regular issues)
> >   Components: deployment, Hot Deploy Dir
> >     Versions: 1.0
> >     Reporter: Aaron Mulder
> >     Assignee: Aaron Mulder
> >     Priority: Critical
> >      Fix For: 1.1
>
> >
> > 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
>
>

Mime
View raw message