Summary: | [code templates] Allow different code templates profiles like formatters & cleanups | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Claudio Nieder <private> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert, laeubi |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Claudio Nieder
2008-09-06 07:07:37 EDT
Makes sense. You probably know this but just in case: you can assign project specific code templates and share them. (In reply to Dani Megert from comment #1) > You probably know this but just in case: you can assign project specific > code templates and share them. I also find that this would be useful. The problem with project specific assignments are that this requires duplicate configuration and if you create a new one it also has to be taken into consideration. What has come into my mind would be to allow to configure a project pattern for a profile that makes it selected on match. For example this could be something like: org.eclipse.* --> "Eclipse built in" org.apache.* --> "Apache Code Format" * --> "Java Defaults" as mentioned by Claudio it would be good if this could be configured on an upper level, so it includes Templates, Cleanup Actions and Code format (the example only shows code format). This would be incredible useful if one needs to manage different projects in a workspace with different rules. |