Bugzilla – Full Text Bug Listing
| Summary: | [preferences] Would like a "project specific settings for everything" option | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Boris Bokowski <bokowski> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, deepakazad, markus.kell.r, remy.suen |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | fix candidate | ||
Btw, I thought I had seen a bug like this before but couldn't find it. >Btw, I thought I had seen a bug like this before but couldn't find it. You probably only looked in JDT. More/better/general support for project specific settings/preferences has been asked and discussed several times before and should be provided by the Platform, see e.g. bug 194414. There are also several requests to turn other non-JDT preferences into project-specific ones. Maybe it's the right time to move the JDT support to the Platform and improve it there. Also interesting/related: bug 200213, bug 300523, bug 293393. |
Currently, project specific settings have to be enabled for every properties page separately (e.g. "Save Actions", "Java Compiler", "Annotation processing", "Building", "Errors/Warnings", etc), and it's easy to miss one or more of them. Ideally, there would be one place with a checkbox like "Enable project specific settings for everything", and as new settings get introduced, these would be project-specific and initialized with default settings automatically. Extra points for anything that makes it easy to have consistent project-specific settings for a number of projects. For example, being able to copy all settings from one project to a number of other projects. Or the ability to name project-specific settings ("Platform UI project settings") such that if any two projects have the same name for their settings but differ in the value of the settings, the projects would be flagged as misconfigured. Or some other solution that I cannot think of right now.