Bugzilla – Full Text Bug Listing
| Summary: | Exclude single file from externalization | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Erwin Tratar <tratar> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | 3.2 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Once migrating to 1.5 source level, you can specify an annotation:
@SuppressWarnings("nls")
class AGeneratedClass {
...
}
Closing, nothing more planned. |
When you are using generated files mixed into your sources while enabling warnings for non externalized strings you get lots of warning/errors in the generated sources. Most often it is not possible to tweak the generation process to add a //$NON-NLS-1$ after every generated string. However, the class comment will probably be configurable, so having something like //$NON-NLS$ /** * or * $NON-NLS$ * or * @NON-NLS */ class AGeneratedClass { ... } could be possible to exclude single files from a) the warnings for non externalized strings and b) from the "Externalize String" Wizard