Community
Participate
Working Groups
It would be really, really great if you could see the full command line actually being run when you launch an external tool. This makes debugging external tool setup way easier.
I thought we added this.
No, we do not print this information out to the log console. I agree, it would be very useful.
Now in the new external tool rework Note: new external tool work is not yet released to the head stream and won't for a while yet.
This bug has not been fixed and should not have been closed.
Java VM processes show the command line used to launch them. We should promote this attribute to the debug core, to allow any process to be annotated with its command line, such that it can be seen from the "properties" pop-up in the debug view.
Fixed - promoted process attribute and property page to debug platform. Program launch delegate annotates process with command line.
Please verify, Jared.
Doesn't appear to work. After executing an ant build script, a target and a process appear in the debug view. Selecting "Properties" on the process brings up the process information dialog, but the "command line:" field is empty. Selecting "Properties" on the target brings up an information dialog that says, "No property pages for ."
This is not for an ant script - it is for a "program" external tool.
adding jared as cc - please see last comment.
I agree we should add the command line info to ant as well - but we do not actually generate a command line for Ant, as it runs in the same VM.
Marking as enhancement to also show equivalent command line for an Ant process launched in the Eclipse VM.
Fixed. Added a "generated" command line for the ant launch configs (see AntLaunchDelegate).
Darin, please verify (add see if there is anything else we should add to the command line).
Verified and slightly modified. I changed the ordering a little and added the input handler and logger options.