geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-752) Unhelpful message when you try to stop a configuration that's already stopped
Date Sat, 27 Aug 2005 18:30:06 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-752?page=all ]

Aaron Mulder updated GERONIMO-752:
----------------------------------

      Component: usability
    Fix Version: 1.0-M5
    Description: 
If you try to stop a configuration that's not running, you previously got an exception or
a message saying that the kernel could not be found.  Since GERONIMO-749 has been fixed, you
get this:

    Error: Deployment failed, Server reports:
    geronimo.config:name="(your config name)" not found

It would be nicer if it said something along the lines of "Module foo is not running".

  was:
If you try to sto pa configuration that's not running, you previously got an exception or
a message saying that the kernel could not be found.  Since GERONIMO-749 has been fixed, you
get this:

    Error: Deployment failed, Server reports:
    geronimo.config:name="(your config name)" not found

It would be nicer if it said something along the lines of "Module foo is not running".

      Assign To: Aaron Mulder
       Priority: Minor  (was: Major)

Currently says:

    Error: foo does not appear to be a TargetModuleID or the name of a
    module available on the selected server.  For a TargetModuleID,
    specify it as TargetName|ModuleName

Should probably say:

    Error: foo does not appear to be a the name of a module
    available on the selected server.  Perhaps it has already been
    stopped or undeployed?  If you're trying to specify a
    TargetModuleID, uset the syntax TargetName|ModuleName

> Unhelpful message when you try to stop a configuration that's already stopped
> -----------------------------------------------------------------------------
>
>          Key: GERONIMO-752
>          URL: http://issues.apache.org/jira/browse/GERONIMO-752
>      Project: Geronimo
>         Type: Improvement
>   Components: deployment, usability
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0-M5

>
> If you try to stop a configuration that's not running, you previously got an exception
or a message saying that the kernel could not be found.  Since GERONIMO-749 has been fixed,
you get this:
>     Error: Deployment failed, Server reports:
>     geronimo.config:name="(your config name)" not found
> It would be nicer if it said something along the lines of "Module foo is not running".

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