geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gianny Damour (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (GERONIMO-2767) Minimize side effects of the offline deployer
Date Fri, 02 Feb 2007 23:15:07 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gianny Damour reassigned GERONIMO-2767:
---------------------------------------

    Assignee: Gianny Damour

> Minimize side effects of the offline deployer
> ---------------------------------------------
>
>                 Key: GERONIMO-2767
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2767
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1.1, 2.0
>         Environment: Offline deployment
>            Reporter: Ted Kirby
>         Assigned To: Gianny Damour
>             Fix For: 1.1.2, 2.0
>
>
> Minimize the side effects of using deployment commands in the "offline" mode. In the
1.1.1 release, offline deployment has the side effect of modifying the server configuration
file to enable all of the modules that are listed in the file var/config/offline-deployer-list:
> geronimo/geronimo-gbean-deployer/1.1.1/car
> geronimo/j2ee-deployer/1.1.1/car
> geronimo/openejb-deployer/1.1.1/car
> geronimo/client-deployer/1.1.1/car
> geronimo/axis-deployer/1.1.1/car
> geronimo/tomcat-deployer/1.1.1/car
> This is undesirable, since an offline deployment should only modify the server configuration
with respect to the deployed module, and not otherwise affect the configuration of the server.
 For example, because of this side effect is not practical to use the following commands to
disable an old version of a module and enable the new version:
> $ bin/deploy.sh --offline stop <moduleId>
> $ bin/deploy.sh --offline start <moduleId>
> Also, the offline deployment feature appears to be broken in the current Geronimo-1.2
branch.
> Finally (and much less importantly), offline deployment appears to modify other files
in the var directory besides the configuration files in var/config (e.g. server log files).
 This presumably happens because offline deployment actually executes geronimo in a limited
way in order to perform the deployment.  Removing this side effect is desirable.

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


Mime
View raw message