Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 176850 - Choosing "Run as|Java Application" on project context too slow
Summary: Choosing "Run as|Java Application" on project context too slow
Status: RESOLVED DUPLICATE of bug 74480
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-09 13:29 EST by Nils Meier CLA
Modified: 2007-03-13 08:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Meier CLA 2007-03-09 13:29:14 EST
I imagine newcomers checking out code from a repository and wanting to "run it" - in worst case choosing one of many types with main() in the same project.

If one chooses "Run as|Java Application" now from the context menu of a Java project in workspace one is confronted with a full list of all workspace classes that implement a main-method.

Apparently there's some logic that puts certain classes at the top of the list but in general I'm still seeing tons of intermixed types that will confuse anyone who just checked out a project say from cvs.

I'd like to propose to change this - if someone chooses Run As|Java Application from the context menu of a project then

1. if there's one type with main() in the project then that type should be executed without prompt

2. in all other cases only types in the project with main() should be listed

There could be a button in the dialog that lets the user choose a working set (default: this project, working set a, working set b, etc.) if someone really expects to run any type from the context-menu of a specific project.

p.s. another thing about the run/debug buttons in the toolbar is that they run the last run/debugged command. IF I choose a project and click run I'd expect that project to be run .. not something I might have opted to run the previous time
Comment 1 Darin Wright CLA 2007-03-13 08:38:13 EDT
This has been addressed in 3.3. See bug 74480 for lanuching the selection vs launch last, and bug 173339 that no longer searches system libraries for main methods in a project.

*** This bug has been marked as a duplicate of bug 74480 ***