[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: -------------------------------------- I have created the UI as described in the mockup. The Alt+Shift+D, D key binding is associated with the Remote Java Application..." action. The Remote Java Application... dialog has the Configure..., Finish and Cancel button. The "Name" field contains the pid of VM. The Ctrl+d+[0-9] key binding, the Remote Debug As menu and the Remote Debug preferences page have been removed. Do you want me to add the "Automatically connect if only one application found" button to the preference page? Aslak, I think I have solved the issue related to the source lookup. Namely, m2eclipse configures a source path provider and class path provider for the following launch configurations: - Java Application - JUnit test - TestNG test but doesn't configure it for a Remote Java Application I have added a source path computer to our configuration that creates a source attachment the same way in which m2eclipse configures a Java Application configuration. I haven't added any m2e dependency. Max, I am still using a separate configuration type. If that isn't a good solution for you, I will try to use the Eclipse's Remote Java Application and add an attribute to the launch config as you suggested. There is a possibility for a conflict if some other plugin would change source path computer of the Eclipse's Remote Java Application. M2eclipse could add such a source path computer. You can add other projects manually, but our Remote Java Application adds automatically all selected projects as well as maven dependencies from the workspace. adds automatically all selected projects and maven dependencies from the workspace to the default source attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira