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-917) Unfriendly error message from mavendeploy:start plugin
Date Wed, 07 Dec 2005 03:48:09 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-917?page=all ]

Aaron Mulder updated GERONIMO-917:
----------------------------------

    Assign To:     (was: Aaron Mulder)

The command-line deploy tool has special handling to see if a module is deployed at all before
calling JSR-88 to start it.  The JSR-88 implementation has special handling to see if a module
is already running,  but would fail with an error if the module was not deployed (I would
guess originating in a NoSuchConfigException or something of the like).  I'm not sure why
the Maven plugin wouldn't be able to interpret or display that correctly, but I'm not the
right one to look into it.  :)

> Unfriendly error message from mavendeploy:start plugin
> ------------------------------------------------------
>
>          Key: GERONIMO-917
>          URL: http://issues.apache.org/jira/browse/GERONIMO-917
>      Project: Geronimo
>         Type: Improvement
>   Components: deployment, usability
>     Versions: 1.0-M4
>     Reporter: Dain Sundstrom
>     Priority: Minor
>      Fix For: 1.1

>
> If you attempt to start a module that  does not exist in the server you get the following
message:
>     Module is already running or may not be deployed: org/openejb/RuntimeDeployer
> We should be able to tell the difference between these two cases as they have vastly
different solutions.
>  

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