Community
Participate
Working Groups
Build Identifier: 20100618-0524 Another "obvious" improvement I couldn't find any report for: As far as I can tell, in "run" or "debug" configuration, you always have to hardcode a project name. This limits the flexibility a lot, especially in terms of shared launch files; there is a good description of the problem here: http://stackoverflow.com/questions/3573933/can-my-eclipse-launch-profile-reference-its-containing-project It also means the debug configuration is not at all symmetric with the build configuration, and I think it would make more sense if it was. In other words, it should be possible to set up launch configurations without an explicit project reference, and have them apply either to the project they are saved under, or the "active" project at a given time. Reproducible: Always
(In reply to comment #0) > In other words, it should be possible to set up launch configurations without > an explicit project reference, and have them apply either to the project they > are saved under, or the "active" project at a given time. How is the "active" project defined?
(In reply to comment #1) > (In reply to comment #0) > > In other words, it should be possible to set up launch configurations without > > an explicit project reference, and have them apply either to the project they > > are saved under, or the "active" project at a given time. > > How is the "active" project defined? The same way as for using build configurations. Maybe "active" isn't the right term, but e.g. the contents of the "Build" and "Manage Configurations" menus are based on data saved in a project, and change according to what you are working on, so a similar notion seems to exist already. I suppose it's related to the selection in the Project Explorer and/or the file opened in the editor currently in focus.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
