Community
Participate
Working Groups
In Eclipse, you can set the file encoding in several different ways and it would be nice if Eclipse recommended the preferred way for all builders/deployers to determine which encoding to use for their output files. Examples: 1. Use the file encoding set explicitly via Eclipse: a. Tries to use the file encoding of the file if it was set directly on the file itself (right-click on file and select the appropriate file encoding) b. Tries to use the file encoding of parent folder(s) of the artifact if set, all the way up to the project folder. c. Tries to use the file encoding set on the workspace (The Editor file encoding set via the Window --> Preferences --> Workbench --> Editors --> File encoding) 2. Uses the file encoding of the JVM (system (OS) default used if not explicitly set in eclipse with the VMArgs "-Dfile.encoding=UTF8" for example. 3. Uses the default file encoding used by the operating system 4. Uses the file encoding of the source file that is being built/deployed Eclipse should give builders/deployers guidance on how to determine the output file encoding to use when generating files so that all builders'/deployers' output will be consistent.
Encodings can be specified in the build.properties of each plugin. Moving to PDE UI for the synchronization issue.
Cheryl, you're talking about builders in the large, and not only PDE plugin/feature builders, right? If so, I'm not sure PDE/UI is the best component for your request (which, if I understand things well, would consist in some sort of API at builder level to know the "right" encoding for a given file). Bug 155015 may be -a bit- similar to this one anyway.
I'll consider this a dupe of bug 155015. Note that this still doesn't cover the individual file case, which I think would be way too expensive to do in a validation routine. This is something that you would have to run elsewhere where a user would know it would take awhile. *** This bug has been marked as a duplicate of bug 155015 ***
