Summary: | Debug/Run "latest" Menus Confusing | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | David E. DeLano <David_DeLano> |
Component: | Debug | Assignee: | Darin Swanson <Darin_Swanson> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P1 | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows All | ||
Whiteboard: |
Description
David E. DeLano
2001-11-02 14:59:52 EST
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. 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. |