[jbosstools-issues] [JBoss JIRA] (JBIDE-11454) Make the status of modules be closer to reality

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790244#comment-12790244 ] 

Rob Stryker edited comment on JBIDE-11454 at 7/17/13 6:01 AM:
--------------------------------------------------------------

Please do not re-open this jira. It has been fixed in 4.1.0.GA to the best of this jira's scope. Anything additional must be a new request. 

> So then why not say something like [Not started]? Just omitting the string "Started" doesn't tell you anything - how is the user supposed to know that he needs to see Started or else something is wrong? U

We do not have control over this decorator. The servers and modules have only 5 possible states.  Started, Starting, Stopped, Stopping, and Unknown. The WTP team has decided that when a state is unknown, the decorator for it is simply omitted. 

Also, declaring it "[Not Started]" sounds the same to most people as '[stopped]', which may not be at all true. It also sounds like you know with certainty that it is 'not started', but in fact we know nothing. The state is 'unknown', and as such, no state is listed. 

Unless you're requesting 'unknown' also get the decorator so that it reads [Unknown, Synchronized] or something of the sort, this won't be changed. 


                
      was (Author: rob.stryker):
    Please do not open another jira, unless you'd like to open a bugzilla for this. 

> So then why not say something like [Not started]? Just omitting the string "Started" doesn't tell you anything - how is the user supposed to know that he needs to see Started or else something is wrong? U

We do not have control over this decorator. The servers and modules have only 5 possible states.  Started, Starting, Stopped, Stopping, and Unknown. The WTP team has decided that when a state is unknown, the decorator for it is simply omitted. 

Also, declaring it "[Not Started]" sounds the same to most people as '[stopped]', which may not be at all true. It also sounds like you know with certainty that it is 'not started', but in fact we know nothing. The state is 'unknown', and as such, no state is listed. 

Unless you're requesting 'unknown' also get the decorator so that it reads [Unknown, Synchronized] or something of the sort, this won't be changed. 


                  
> Make the status of modules be closer to reality
> -----------------------------------------------
>
>                 Key: JBIDE-11454
>                 URL: https://issues.jboss.org/browse/JBIDE-11454
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>         Environment: JBoss Developer Studio 5 Beta
> JBoss Enterprise Application 6 Beta
>            Reporter: Mustafa Musaji
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.1.0.CR1
>
>
> When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize this as failure and continues to report the status as [Started, Synchronized].
> This a request to add the ability for JBDS to report back via the console when a deployment fails due to application errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira