You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ted Kirby (JIRA)" <ji...@apache.org> on 2007/01/22 21:30:30 UTC

[jira] Created: (GERONIMO-2767) Minimize side effects of the offline deployer

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
             Fix For: 2.0, 1.1.1


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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Assigned: (GERONIMO-2767) Minimize side effects of the offline deployer

Posted by "Gianny Damour (JIRA)" <ji...@apache.org>.
     [ 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.

[jira] Closed: (GERONIMO-2767) Minimize side effects of the offline deployer

Posted by "Gianny Damour (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gianny Damour closed GERONIMO-2767.
-----------------------------------

    Resolution: Fixed

This is now fixed.

> 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.

[jira] Updated: (GERONIMO-2767) Minimize side effects of the offline deployer

Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated GERONIMO-2767:
-----------------------------------

    Fix Version/s:     (was: 1.1.1)
                   1.1.2

updating 1.1.1 fix version to 1.1.2

> 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
>             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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira