[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8548) Support auto discovery of remote processes for debugging
[
https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-8548:
--------------------------------------
Aslak,
I can reproduce your issue related to the source lookup. It happens because the Maven
classpath container adds only the output directory (target/classes) to the classpath.
Eclipse can't find source on the basis of the output directory. The same issue happens
when creating a debug session using the Eclipse's Remote Java Application
configuration. It can be solved.
I will check if it is possible to use MavenRuntimeClasspathProvider without adding m2e
dependencies to the remote.debug plugin. M2eclipse uses MavenRuntimeClasspathProvider to
solve classpath dependencies.
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, lsof.txt,
org.jboss.tools.remote.debug.zip, org.jboss.tools.remote.debug1.zip,
org.jboss.tools.remote.debug2.zip, 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: http://www.atlassian.com/software/jira