[
https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin...
]
Aslak Knutsen commented on JBIDE-8548:
--------------------------------------
I'm seeing these, but they might be expected?
{code}
The command ("org.jboss.tools.remote.debug.ui5951") is undefined
The command ("org.jboss.tools.remote.debug.ui.configure") is undefined
{code}
The launch configuration does not change "Project" after first creation.
# select project 1 - remote debug
# select project 1 - configure
** "default" remote debug launch will be associated with project 1
# disconnect debug
# select project 2 - remote debug
# select project 2 - configure
** "default" remote debug launch is still associated with project 1
Just tested it for 5 min, but really nice! :)
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.M3, 3.3.x
Attachments: 8548-1.png, 8548-2.png, 8548-3.png,
org.jboss.tools.remote.debug.zip
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