Community
Participate
Working Groups
The debug and run menus give a list of the latest commands at the top. However, this list appears to be shared, and selecting an entry that was previously a run from the debug menu causes a run, not a debug. This is confusing. Also, there is no information in the menu indicating whether the command was a debug or run. I can see at least three ways to resolve this: Each menu should have it's own latest menu. The menu contains info as to whether the command is run or debug. The command takes the context of the menu it is in. More info on the third option: Let's say I run a java application. I then want to debug it. It shows up on the debug "latest" list, but rather than submitting a run again, it submits a debug for the same program.
The intended behavoir is the 3rd option. This used to work.
I did some more testing on this, and it actually works better than it did. Once, I ran a command from debug and got a run instead. However, after I got the response that option 3 is what is intended, I went back and tested with the current state I'm in. If I select any of the entries in the list from debug, I get debug. If I select from run, I get debug. Before, I was always getting a run from debug. Another suggestion. Even if something fails, add it to the list. This is especially true with remote debugging. When you are having problems, and you have to continually type in all the info because it failed the last time you ran it, it would be appreciated to add it to the list.
The IDE died on me, so I had to restart it. This time I did a run, the selected the entry from the debug menu. It did a run instead of a debug.
Logged "add failed" feature request as bug 5534.
I cannot reproduce on the latest code stream. What drop are you using? Can you give a detailed test case for the problem: exact launcher used etc. Sending me your launchHistory.xml may help as well which can be found in ..\.metadata\.plugins\org.eclipse.debug.ui in your workspace directory. Thanks
WSDD build 0.6.30 WSW build 0.137 I think this is from the 10/31 drop. Select a class and click on the run icon. Select Run Java Application. Close the application. Click on the debug icon and select the application out of the history menu. As I understand it, this should debug that application. Instead, it runs. I tried to attach the file you suggested, but there is none. The folder exists, but it is empty.
This is fixed in the 2.0 stream. It could also be that this is a problem in the VAME 1.0 strem, as VAME added extra run/debug actions to the toolbar that had their own implementations.
