geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-1285) Deployer does not list all modules that have been stopped
Date Fri, 11 May 2007 16:28:15 GMT

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

Donald Woods resolved GERONIMO-1285.
------------------------------------

    Resolution: Fixed

Slight rework, to remove the extraneous updateStatus() calls when processing the childs.
Also updated StopCommand to display "Module <id> is already stopped" instead of treating
it as a failure.
Rakesh, thanks for the patches.

> Deployer does not list all modules that have been stopped
> ---------------------------------------------------------
>
>                 Key: GERONIMO-1285
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1285
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>         Assigned To: Donald Woods
>            Priority: Critical
>             Fix For: 2.0-M6
>
>         Attachments: consoleprint1285.patch, deploytooloutput.patch
>
>
> When you, for example, stop the "tomcat" configuration, all the web apps deployed to
Tomcat are stopped too.  However, the deployer does not let you know this.  It should list
all modules that were stopped, just like it does when starting.

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