Summary: | Extension point "org.eclipse.jdt.core.codeFormatter" is ignored | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Arno Unkrig <arno> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | amj87.iitr, daniel_megert, markus.kell.r, Olivier_Thomann, srikanth_sankaran | ||||
Version: | 3.6 | ||||||
Target Milestone: | 3.6 M7 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Arno Unkrig
2010-04-20 07:06:43 EDT
To be precise, it is source file line 169: return new DefaultCodeFormatter(currentOptions); This extension point is deprecated as it must be defined through a deprecated interface. What you really want is a new extension point that would reflect the new way to instantiate a code formatter. This is an enhancement for 3.7. I'm not sure if it makes sense to support "pluggable" code formatters. We have a lot of references to DefaultCodeFormatterConstants and make assumptions about how the formatter works, so I doubt you would get happy with just an extension point. I agree with Markus. We should clarify the Javadoc and mark the extension point deprecated. Created attachment 165534 [details]
Fix
Please mark the codeFormatter.exsd file as ASCII (Team > Change ASCII/Binary Property...).
Released for 3.6M7. Thanks for the patch. Verified for 3.6M7 through code inspection Verified. |