Community
Participate
Working Groups
Build ID: I20090611-1540 Steps To Reproduce: 1. Create any kind of plugin project 2. Add a string to any of its classes (directly within the java source) 3. Include any kind of output method to show that string More information: If "Use class files compiled in workspace" is NOT enabled in the Options tab, then it seems that during compilation the file encoding is not passed to the java compiler resulting in class files that show strings as they were originally ANSI encoded, even though they are supposed to be e.g. UTF-8 encoded. If the above option is enabled, class files are generated as expected. (This applies both to container wide file encoding settings (Properties->Resource->Text file encoding on a project) and to individual file encoding settings (Properties->Resource->Text file encoding on a single file).
I just read that this bug was assigned to JDT UI. I'm not quite sure, if this is correct. Probably my explanation was not accurate enough. When the plugin is run from workspace, no problem occurs; only after an export of a plugin. (The dialog that I am referring to can be accessed via plugin.xml->Overview->Export Wizard or right click on a project->Export->Plugin-Development->Deployable plugins and fragments.)
The plug-in export wizard is from PDE/UI. Moving back. This sounds like bug 155015, but that should be fixed in 3.5.
You're completely right. It's a duplicate of bug 155015. But 155015 seems to never have been properly fixed. That's why this problem occured again. *** This bug has been marked as a duplicate of bug 155015 ***
