[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8548) Support auto discovery of remote processes for debugging

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614653#comment-12614653 ] 

Snjezana Peco commented on JBIDE-8548:
--------------------------------------

I have updated the Remote Debug plugin.
It includes the following features/fixes:

> I see what is happening now. They are removed, but..

>    Select a Class in the "Package Explorer"
>   Press "Debug As -> Debug Configuration"
>   Select "JBoss Tools Remote Java Application"
>    Right click -> New

> It now creates 2 configurations, one named the same as the selected Class in step 1 and one called "New_configuration"

Fixed.

> Seems it has problems auto recreating the launch config?

>    select a resource/class, shift + alt + D + D, it connects to your running service
>    disconnect from debug mode
>    debug as -> debug configuration
>    delete all "JBoss Tools Remote Java Application" configurations
>    with the same resource/class selected, shift + alt + D + D, nothing happens?

> When the configuration is manually deleted, it is not auto recreated. Error log show:

Fixed.

> Has the "Preferences" Page been removed? I wanted to uncheck the "auto connect if only one found" option. 

I have reverted the preferences page which now contains only the "Automatically connect if only one application found" checkbox.


The issue related to the source lookup for the https://github.com/ALRubinger/jboss-as-test-example project 

Fixed.
The problem was because the project includes arquillian as well as some other dependencies having the test scope.
I have resolved the source lookup using the m2e's source path computer that is created for the Java Application launch configuration type. 
This source path computer adds only those artifacts that have the runtime, provided and system scope.
I have fixed the problem so that our source path computer now also adds artifacts that have the test scope.
This will add unnecessary entries to the source lookup sometimes that may only affect performance.
We have to add all the entries because we never know if some remote application is executed in the test or runtime scope. 
It would be possible to add the scope attribute to our configuration which would, in my opinion, confuse users and would have no significant effect on performance.


> 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, org.jboss.tools.remote.debug3.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