You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Sing Li (JIRA)" <de...@geronimo.apache.org> on 2005/06/14 15:28:48 UTC

[jira] Created: (GERONIMO-674) Deployer list-modules command to display state info of configurations

Deployer list-modules command to display state info of configurations
---------------------------------------------------------------------

         Key: GERONIMO-674
         URL: http://issues.apache.org/jira/browse/GERONIMO-674
     Project: Geronimo
        Type: New Feature
  Components: deployment  
    Versions: 1.0-M4    
    Reporter: Sing Li


It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.

Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.

The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1

With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. goto 1


-- 
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-674) Deployer list-modules command to display state info of configurations

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-674?page=all ]

Aaron Mulder updated GERONIMO-674:
----------------------------------

    Fix Version: 1.0-M5

> Deployer list-modules command to display state info of configurations
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-674
>          URL: http://issues.apache.org/jira/browse/GERONIMO-674
>      Project: Geronimo
>         Type: New Feature
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Sing Li
>     Assignee: Aaron Mulder
>      Fix For: 1.0-M5

>
> It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.
> Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.
> The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1
> With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. start dependent config  5. goto 1

-- 
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] Assigned: (GERONIMO-674) Deployer list-modules command to display state info of configurations

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-674?page=all ]

Aaron Mulder reassigned GERONIMO-674:
-------------------------------------

    Assign To: Aaron Mulder

> Deployer list-modules command to display state info of configurations
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-674
>          URL: http://issues.apache.org/jira/browse/GERONIMO-674
>      Project: Geronimo
>         Type: New Feature
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Sing Li
>     Assignee: Aaron Mulder

>
> It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.
> Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.
> The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1
> With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. start dependent config  5. goto 1

-- 
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-674) Deployer list-modules command to display state info of configurations

Posted by "Sing Li (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-674?page=all ]

Sing Li updated GERONIMO-674:
-----------------------------

    Description: 
It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.

Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.

The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1

With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. start dependent config  5. goto 1


  was:
It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.

Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.

The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1

With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. goto 1



> Deployer list-modules command to display state info of configurations
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-674
>          URL: http://issues.apache.org/jira/browse/GERONIMO-674
>      Project: Geronimo
>         Type: New Feature
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Sing Li

>
> It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.
> Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.
> The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1
> With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. start dependent config  5. goto 1

-- 
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-674) Deployer list-modules command to display state info of configurations

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-674?page=all ]
     
Aaron Mulder closed GERONIMO-674:
---------------------------------

    Resolution: Fixed

Revision 263877

> Deployer list-modules command to display state info of configurations
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-674
>          URL: http://issues.apache.org/jira/browse/GERONIMO-674
>      Project: Geronimo
>         Type: New Feature
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Sing Li
>     Assignee: Aaron Mulder
>      Fix For: 1.0-M5

>
> It is frustrating, before a whiz bang GUI console becomes available, to have to start DebugConsole each time one needs to find out if a configuration has silently failed.
> Since the deployer already has a list-modules command, showing all the configurations, it would be ideal to have the state of the configuration listed as a column next to the ids.
> The typical use-case today is ->   1. try to deploy   2. deployment failed, don't know why  3. startup DebugConsole 4. find a browser to see the DebugConsole UI  5. determine that dependent config has stopped 6.  start dependent config  7. goto 1
> With the status added ->  1. try to deploy 2. deployment failed, don't know why   3.  list-modules with deployer and determine dependent module has stopped  4. start dependent config  5. goto 1

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