Bug 39801

Comment 1 Debbie Wilson 2003-07-09 10:53:47 EDT

I'm not sure what you are referring to here.  Are you referring to those 
projects that are listed in the Package Explorer view or the Navigator view or 
in some debug information you are printing out or in your .log file?  Could 
you provide explicit details (perhaps a concrete example) on what you are 
seeing and what you would expect to see?

Comment 2 Peter Kidson 2003-07-10 12:01:56 EDT

The package Explorer view.

Let's say I have ProjectA and ProjectB, each of which contains a number of 
different programs, each of which has its own launch (bear in mind a launch is 
associated with only one project).   

If I am working in ProjectA (ProjectA open and ProjectB closed), I wouldn't be 
wanting to launch any of the programs in ProjectB, and vice-versa.  However the 
launch pull-down list always shows all the launches - those for ProjectA as 
well as all those for ProjectB.  

What I am suggesting is that when, say, only ProjectA is open, the launch pull-
down should only show launches associated with ProjectA.

   

Comment 3 Tod Creasey 2003-07-21 13:45:21 EDT

This is handled by the Debug component.

Comment 4 Jared Burns 2003-08-05 13:06:13 EDT

If you place a launch configuration inside a project (configured on the "Common" 
tab) and later close that project, the configuration is removed from the menu.

The "Project" attribute of the Java launch configuration type is only known to 
the Java launching support. Generically, launch configuration's don't have a 
Project, so the menu (which doesn't know about Java launching) can't exclude 
configs based on this attribute.

Comment 5 Peter Kidson 2004-06-02 03:45:01 EDT

Now using 3.0 M9, on W2K.

As regards the first point, I have not found this to be the case. The launches 
of closed projects are still listed, even though in their common tab the "Type 
of launch configuration" is Local, and neither of the "Display in favorites 
menu" options is checked.

As regards the second point, does this not contradict the first point?  If as 
you say the menu can't know the launches' projects, how can it know to exclude 
the launches of closed projects?

Essentially what I am suggesting/requesting, is that the project attribute of a 
launch SHOULD be made public; so that, for example, the menu module can know 
which launches to display and which ones not to.   

(This becomes increasingly relevant as your projects and launches increase in 
number).

Comment 6 Darin Wright 2004-06-02 09:25:57 EDT

In commnet#4, note that we said "shared" configs are not displayed when their 
project is closed - i.e. stored as a file in the workspace (rather than 
locally with with workspace metadata). Local configs are still displayed when 
their project is closed. I'm now marking this as a dup of bug 19521.

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