]
Max Rydahl Andersen commented on JBIDE-8548:
--------------------------------------------
Just updated - this UI is *much* better IMO - no blockage and its informative ;)
I found a few "gotchas":
* The progress bar shows "Discover VM PID=489" when waiting for a java that is
waiting for connection.
That's not very clear to the user what that means and how many processes does it
need to wait for ;)
I suggest something like "1 out of 3: Discovering port, main class and arguments
for process id 489"
* Putting in background and starting a second "Remote Java Application" causes
two scans to occur and wait for each other and eventually show the main dialog twice. I
suggest showing a dialog saying "Remote Java Application scan already in progress.
Please wait for it to be complete." and then if doable have a "Bring scan to
foreground" button next to a "Ok" and "Try again" button.
* When Class is Unknown it just says Unknown in the class column - I would leave it blank
or put "<Unknown>" to signify the class is actually not named Unknown.
* Name column I assume should actually be PID or Process ID ?
* Finish is probably better named as "Connect" or "Launch" ?
* Using the name "Default" is not really good for default configuration - I
suggest using the same name Run As/Debug As would give to a launch (i.e. the project
name). In case of multiple projects selected then I would use "myapp + N more"
where myapp is the project for the first element and N is the number of projects. Or if
just to be simple just "myapp"
Maybe add "Remote " as prefix ?, so it becomes "Remote myapp" ?
* It seems I can't do Remote Debug on other selections than a Project resource ?
Couldn't it just take the project of the current selected resource ?
* ...and I still think using normal Remote Java Applications config would be the best
approach for this functionality; and allow user to choose if there are any ambiguity.
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,
org.jboss.tools.remote.debug4.zip, org.jboss.tools.remote.debug5.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: