You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org> on 2005/08/25 21:14:08 UTC
[jira] Created: (GERONIMO-917) Unfriendly error message from mavendeploy:start plugin
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.0
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
[jira] Updated: (GERONIMO-917) Unfriendly error message from mavendeploy:start plugin
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-917?page=all ]
Dain Sundstrom updated GERONIMO-917:
------------------------------------
Fix Version: 1.1
(was: 1.0)
Assign To: Aaron Mulder
Aaron did you already fix this? If not, we don't need to fix it for 1.0.
> 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
> Assignee: Aaron Mulder
> 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
[jira] Closed: (GERONIMO-917) Unfriendly error message from
mavendeploy:start plugin
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-917?page=all ]
Matt Hogstrom closed GERONIMO-917.
----------------------------------
Resolution: Won't Fix
Really old issue...reopen if needed. Given the significant change since this was opened and the lack of comments I'm closing this issue.
> Unfriendly error message from mavendeploy:start plugin
> ------------------------------------------------------
>
> Key: GERONIMO-917
> URL: http://issues.apache.org/jira/browse/GERONIMO-917
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Maven Plugins for G
> Affects Versions: 1.0-M4
> Reporter: Dain Sundstrom
> Priority: Minor
> Fix For: 1.2
>
>
> 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
[jira] Updated: (GERONIMO-917) Unfriendly error message from mavendeploy:start plugin
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-917) Unfriendly error message from
mavendeploy:start plugin
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-917?page=all ]
Aaron Mulder updated GERONIMO-917:
----------------------------------
Component: Maven Plugins for G
(was: deployment)
(was: usability)
> Unfriendly error message from mavendeploy:start plugin
> ------------------------------------------------------
>
> Key: GERONIMO-917
> URL: http://issues.apache.org/jira/browse/GERONIMO-917
> Project: Geronimo
> Type: Improvement
> Components: Maven Plugins for G
> 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