]
Snjezana Peco commented on JBIDE-8548:
--------------------------------------
I have added all the suggestions you described in the previous comment.
Now, the Remote Debug plugin uses the Eclipse Remote Java Application configuration. It
changes those Eclipse Remote Java Applications that are marked as JBoss Remote
Configuration.
Such configurations can be created using the standard Eclipse Remote Java Application tab
(the JBossRemoteConfiguration.png screenshot). The user can also choose some of these
configurations when launching a debug session within the Remote Java Application dialog
(the RemoteJavaApplication1.png screenshot).
The source code is on
. The update site hasn't
been changed.
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, jbide-8548d.png,
JBossRemoteConfiguration.png, lsof.txt, org.jboss.tools.remote.debug.zip,
org.jboss.tools.remote.debug1.zip, org.jboss.tools.remote.debug2.zip,
org.jboss.tools.remote.debug3.zip, org.jboss.tools.remote.debug4.zip,
org.jboss.tools.remote.debug5.zip, RemoteJavaApplication1.png,
remote_java_application.bmml
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: