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] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped
Date Wed, 06 Dec 2006 12:52:21 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Rakesh Midha updated GERONIMO-1285:
-----------------------------------

    Assignee:     (was: Rakesh Midha)


I did both the items I was thinking to do for this JIRA. Added patch for deploy tool as well
as console to prnt all the module names stopped, started, uninstalled

Marking patch available, unassigning so that someone can review and commit

> Deployer does not list all modules that have been stopped
> ---------------------------------------------------------
>
>                 Key: GERONIMO-1285
>                 URL: http://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
>            Priority: Critical
>             Fix For: 2.0
>
>         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.
-
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