176413 – Eclipse Product Export Wizard fails when encoding is set to UTF-16

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 176413 - Eclipse Product Export Wizard fails when encoding is set to UTF-16

Summary: Eclipse Product Export Wizard fails when encoding is set to UTF-16

Status:	RESOLVED DUPLICATE of bug 155015

Alias:	None

Product:	PDE
Classification:	Eclipse Project
Component:	Build (show other bugs)
Version:	3.2.1
Hardware:	PC Windows XP

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	pde-build-inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-03-05 15:50 EST by Aaron Cohen
Modified:	2009-01-07 19:02 EST (History)
CC List:	3 users (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 Aaron Cohen

2007-03-05 15:50:54 EST

Build ID: 3.2.1

Steps To Reproduce:
1. Set Workspace default encoding to UTF-16
2. Create a sample Hello RCP App
3. Create a product configuration
4. export it to a directory. This is where it fails
Do the same with the default encoding set back to cp1252 or US-ASCII and it works without a problem.


More information:
If the Java code is created with UTF-16 as the default encoding, the RCP app cannot be exported.

Comment 1 Andrew Niefer

2007-03-06 13:49:46 EST

I haven't had time to try this yet, is it the compile that is failing?

Note that you can set the encoding to pass to javac in your plugin's build.properties file:

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.  

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

Comment 2 Sergei A. Klochkov

2007-10-26 10:45:41 EDT

Also see bug 155015.

Comment 3 Benjamin Cabé

2009-01-07 18:59:13 EST

This is indeed very likely a dupe of bug 155015. Chris?

Comment 4 Chris Aniszczyk

2009-01-07 19:01:45 EST

This looks like the typical encoding issue.

I'll assume it's the same. Please reopen if it's otherwise.

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

Comment 5 Chris Aniszczyk

2009-01-07 19:02:05 EST

btw, Thanks Benjamin ;)