Bug 274786 - PDE build lacks compiler encoding parameter
Summary: PDE build lacks compiler encoding parameter
Status: RESOLVED DUPLICATE of bug 260997
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 03:54 EDT by Stefan Flick CLA
Modified: 2009-05-04 10:05 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Flick CLA 2009-05-04 03:54:45 EDT 
One of our customers has a legacy rule, that forces all source files to be encoded in UTF-8. So the projects resource encoding is UTF-8 (inherited from container).
When compiling the bundle project PDE and run via a launch configuration inside the eclipse IDe everthing is fine. But when exporting a bundle/product, those settings are ignored and the result are corrupted strings when they contain special characters.
Comment 1 Andrew Niefer CLA 2009-05-04 10:05:50 EDT 
The options to control encoding during export/headless build are
# javacDefaultEncoding.<library> - sets default encoding to use when compiling the given library.
# javacCustomEncodings.<library> - a comma separated list of paths and encodings to use when compiling the given library.  Example:

javacCustomEncodings.library.jar = src/org/foo[US-ASCII], src/org/foo/bar.java[ISO-8859-1]

Bug 260997 was about synchronizing these properties with the workspace settings, marking this as a duplicate of that.

*** This bug has been marked as a duplicate of bug 260997 ***