[
https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-8548:
--------------------------------------------
Yes and Yes to both Aslak and Snejzana ;)
The flow would be to have Debug As -> Remote application... (try to only enable it when
relevant to avoid cluttering the menu always, maybe only enable it on project root nodes
?)
Then show the list of running applications with all the information that the API can/will
provide (ports, vmargs etc.) so its easier to find the possible app and then simply setup
that remote process via the standard JDT/Debug Attach to remote java app launch configs.
It should also be possible to run it explicitly without the "Debug As..." so
providing a Command that users can invoke via Ctrl+3 or via the Debug menu would be
perfect too.
Support auto discovery of remote processes for debugging
--------------------------------------------------------
Key: JBIDE-8548
URL:
https://issues.jboss.org/browse/JBIDE-8548
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Fix For: 3.3.0.M2, 3.3.0.M3, 3.3.x
It would be helpful if Eclipse could provide a 'debug as' with auto discover of
local java processes, somewhat like jconsole does. Eclipse should also auto associate the
debug session with the current project.
'debug as' -> 'remote process x'
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira