[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Galder Zamarreno updated JBIDE-2700: ------------------------------------ Environment: Nightly build: 200808190012 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-2700: ------------------------------------ I know a menu item (show in -> console) was added to the server view. I am not sure what code behind the scenes has made the showing no longer automatic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-2700. -------------------------------- Resolution: Won't Fix Labels: new_and_noteworthy (was: ) I've now replicated and traced it way back to its origin. The basic gist of it is that if the "DebugUI" plugin has *not* been loaded in your workspace yet. If you switch to the debug perspective and then back to JBoss AS perspective, the console should show up on start and stop. While I've found no bug reports on WTP on this, WTP obviously made a conscious decision to add a "show in" menu to the view to deal with this problem. The only alternative is for me to forcefully require that the "DebugUI" plugin be started when my plugins are started, or to stick with the current use case as presented by wtp. Being as eclipse is a lazy-load environment, I think it would be wrong of me to forcefully start the entire DebugUI plugin for consoles to start, and so I suggest to you instead to use the "Show in -> Console" UI. Closing as "Won't Fix", however I feel this issue should be added to the release notes, so I'm labeling it new_and_noteworthy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Max Rydahl Andersen reopened JBIDE-2700: ---------------------------------------- Just reopening to hear what you want added to the release notes ? I don't see much new and noteworthy about this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2700: -------------------------------------------- So that is something that should be added to the documentation, not new and noteworthy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2700: -------------------------------------------- We have release notes for JBDS where i can put it but for jbosstools the best place is to have it in the actual docs since this will be and have been like this forever. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] John Graham reopened JBIDE-2700: -------------------------------- The WTP bug has been resolved, and I imagine we've picked up that build already. Since this is still happening in CR2 builds, either the WTP bug did not fix the issue, or we have a different problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2700: --------------------------------------- Component/s: UpStream (was: JBossAS) Fix Version/s: LATER (was: 3.0.0.beta1) so this wont be able to be closed before WTP 3.1 gets out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Jiri Peterka reopened JBIDE-2700: --------------------------------- Seen this issue in JBDS 2.1.1.GA. Build id: v200911051555R EAP 5.0, Linux 64 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-2700. -------------------------------- Resolution: Done As is shown above, and in the eclipse bugzilla link, this is fixed in WTP 3.1 streams. JBDS 2.1.1 is based on the WTP 3.0.x maintenance stream, specifically WTP 3.0.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-2700. -------------------------------- Resolution: Won't Fix What was fixed specifically is that you can go to the server and right-click it and select show in -> console. (This previously had been broken) The reason the console does not always show up automatically is because the debug ui plugin is *NOT* loaded, and no action is being taken to LOAD the plugin. Starting a server does not load the debug ui plugin, and the logic according to WTP is that it SHOULD NOT load the plugin either. However, what was fixed by WTP, and what works currently, is right-clicking the server and selecting "show in -> console". This *will* load the debug ui plugin and from then on the console will work. This is working 100% as designed. I am closing this bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2700?page=com.atlassian.jira.plu... ] Dominik Pospisil commented on JBIDE-2700: ----------------------------------------- Any comment on this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira