Please do any work in the 1.1 branch. Right now 1.2 is in a very uncertain state. Though, I suspect the issues will be different in 1.1, so you may want to start by testing the same things there.
IIRC, the hot deployer does not yet check the timestamp of the deployments in it its directory during startup and compare those to the timestamps of the current modules to determine whether an existing file there is the same as ever or a new version was copied in while the server was down. That should be doable in 1.1. Thanks, Aaron On 5/4/06, Rakesh Ranjan <[EMAIL PROTECTED]> wrote:
Thanks Aaron for the quick response. Here are two issues with Geronimo-1.2-SNAPSHOT which need to be fixed : 1. When Geronimo starts, it try to deploy the modules in the hot deployment directory even if that module is already deployed. Since the application is already deployed, it throws an error : the application already exists in the server. 2. Geronimo is not able to deploy the database plans kept in the hot deployment directory. Rakesh Ranjan On 5/4/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > You're welcome to look at that. Can you list the issues you're going > to attempt to fix? There seems to be a lot of variation in what > people think the problems actually are. > > Thanks, > Aaron > > On 5/4/06, Rakesh Ranjan < [EMAIL PROTECTED]> wrote: > > Hi all, > > > > I have not seen much activity in hot deployment directory enhancement. I > > have seen there are some bugs in the current implementation of hot > > deployment directory. I am interested to work on this enhancement. So i want > > to know the current status of this enhancement? Is some other member working > > on this issue? > > > > Rakesh > > >
