Bug 274786

Summary:	PDE build lacks compiler encoding parameter
Product:	[Eclipse Project] PDE	Reporter:	Stefan Flick <stefan.flick>
Component:	Build	Assignee:	pde-build-inbox <pde-build-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer
Version:	4.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Stefan Flick

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

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 ***