[
https://jira.jboss.org/jira/browse/JBIDE-5739?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5739:
------------------------------------
To clarify, the workspace as a whole will not take longer to start up since debug.ui is
not being loaded at workspace-startup. However debug.ui is now being launched / started
exactly 3 seconds after you first try to start a server.
This should not noticably impact the server startup time because we're not switching
perspectives or loading any views. This should be the minimal amount of debug.ui loading
that is necessary for showing the console output, and I have not noticed any significant
further delays. So I think this should be fine.
Missing Server Console
----------------------
Key: JBIDE-5739
URL:
https://jira.jboss.org/jira/browse/JBIDE-5739
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR1
Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1
Reporter: Burr Sutter
Assignee: Rob Stryker
Fix For: 3.1.0.CR2
Attachments: Console_Tab_Issue.pdf
The Console Tab (Java EE perspective) does not display the server output upon a new
installation nor after an "eclipse.exe -clean".
See attached document for my flow.
The workaround was captured by Aaron in this document:
http://community.jboss.org/wiki/SOA-P43WorkshopLabExamples
Page 22 of the PDF file says
"Sometimes the console tab does not show the output of the server. If it does not,
click on the "Console" tab, select the dropdown icon in the top right corner of
the console tab and choose "Java Stack Trace Console". Then, you should see more
icons to the left of the dropdown you selected. Select the next dropdown to the left and
choose "SOA-P 4.3 Server"."
--
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