| Summary: | Use shared configuration for test workspaces by default? | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | John Arthorne <john.arthorne> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Interesting... As you know, though, configuration areas can be used to store preferences and other metadata. So if this all of a sudden becomes the default behavior, the once-distinct launch configurations will start interfering with each other, which might confuse people. Might be a good idea to have as an option though. |
Build: 3.1 M3 I have a large number of PDE JUnit test launch configurations for various test suites that I run (about 50). Each time I create a new launch config for a new test, it creates a new configuration directory for that test. However, all of these launch configs are using an identical plugin configuration ("Launch with all workspace and enabled external plugins" is selected for all of them). I realize that I have the option to pick the same configuration location for all of these tests, but that is tedious to change for all 50 launch configs. As a result, the org.eclipse.pde.core directory in my .metadata folder has nearly 100MB of disk space used for all the configuration metadata. I was wondering if it would make sense to have a "default" configuration under .metadata/.plugins/org.eclipse.pde.core. This default config would be used for all launches that run with all workspace and external plugins (the default setting for PDE launch configs). That way, all of my 50 test launch configs would be sharing a single eclipse configuration directory, and lots of disk space would be saved.