geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-1431) Make deploy tool and hot deploy directory work better together
Date Tue, 21 Nov 2006 12:47:03 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1431?page=comments#action_12451624 ] 
            
Rakesh Midha commented on GERONIMO-1431:
----------------------------------------


Fixed all the problems dscussed in this JIRA.

1. If deploy using deploy tool and copy new version into hot deploy dir, redeploy
2. If deploy using hotdeploy and add another form of it in hotdeploy, repdeploy

Changes included in this patch:
Modifies isFileDeployed method, earlier it was useful only during initialization , now it
checks deployed status anytime during server lifespan. It used deployment manager to get the
deploy information
During new file hot deploy, check if module with same configId already exists, if yes redeploy
and delete earlier hotdeploy directory.

This patch is dependent on patch https://issues.apache.org/jira/secure/attachment/12345398/hotdepoystartup.patch
provided in https://issues.apache.org/jira/browse/GERONIMO-2584, otherwise it will give compiletime
error.






> 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
>         Assigned To: Rakesh Midha
>            Priority: Critical
>             Fix For: 1.2
>
>
> 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