Bugzilla – Full Text Bug Listing
| Summary: | Run configurations should be saved in the .project file | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Robert (Kraythe) Simmons <robert.simmons> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Robert (Kraythe) Simmons
As an addendum, the run configurations might be available from the project properties as well. Move to JDT/Debug Can you give some more details about what you have in mind? We already have a few stories for launch configurations: 1. Non-shared (default) launch configurations - These configs are stored in the metadata. Storing these configs with the project would defeat their "non-shared" nature. So nothing will change here. 2. Shared launch configurations - Configurable on the Common tab, you can choose to have the config file written wherever you want in the workspace. This puts configs in a project and is probably what you're looking for. 3. Project builders - Go to the Builders tab of the projet properties and you'll see that you can add and configure launch configs. These configs are stored in the project and run as builders via the .project file. If you have configs that you want to be run with each build of a project, this will do the job. Is there something more that you need? Marking as works for me. No additional work planned. Well, that is a little rude. You could at least give me time to reply. I am aware that you can configure builder tools to do various build activities. Im afraid that perhaps I wasnt clear enough. What I mean is in a project you often select an editor in the project and use "Run" toolbar icon; then the run configuration window will pop up. At which point you can add a new configuration for applet or application or workbench. Except in the case of shared configurations, these are almost always specific to the project. For example, If I create a run configuration to test my SLeak plugin, I want to have certain plugins active and others not. However, if Im testing the memory debug graph that Im working on then I want to have completely different plugins active. This is even more the case when developign client software for a customer. The run configurations are specific to the project. So I would suggest that all Non-shared run configurations are saved in the project file from which they are created. Obviously shared configs will be saved in the workspace as before. With this change the behavior would be that when the user opens a particular project, their run configurations will be added to the run menu for use. If they subsequently close the project, these configurations would be removed from the run menu. In closing, I would like to say that I am re-opening the bug and I dont think it is terribly useful to close things before there is understanding on what the issue is. I beleive this is the same request as bug 19521 - i.e. when a project is closed, do not show it's associated launch configurations. This bug report suggests to use the .project file as a solution. However, the .project file is shared in the repository with other developers, and is thus not the correct solution (this would mean all configs are shared with all developers). Propose to mark as duplicate of bug 19521. |