Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343422 - [javadoc wizard] Generating Javadoc for CUs with UTF-8 names fails on Windows
Summary: [javadoc wizard] Generating Javadoc for CUs with UTF-8 names fails on Windows
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7 M7   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-20 10:37 EDT by Dani Megert CLA
Modified: 2011-04-20 10:46 EDT (History)
1 user (show)

See Also:

Attachments
Fix (2.82 KB, patch)
2011-04-20 10:46 EDT, Dani Megert CLA 		no flags Details | Diff
View All 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 Dani Megert CLA 2011-04-20 10:37:55 EDT 
3.6.

Generating Javadoc for CUs with 'UTF-8' names fails on Windows (where 'Cp1252' is the default encoding).

1. start new workspace
2. import project form attachment 193329 [details]
3. set project encoding to UTF-8
4. try to export Javadoc
==> fails because the file names are mangled

There's no way to fix this by using VM arguments or extra Javadoc program arguments because the options file is created using the encoding with which the workspace was launched and the '-encoding' parameter is not used when reading the options file.
Comment 1 Dani Megert CLA 2011-04-20 10:44:27 EDT 
If the encoding for the 'javadoc' command is specified using "-J-Dfile.encoding=MY_ENCODING" then we should use that to write the options file.
Comment 2 Dani Megert CLA 2011-04-20 10:46:07 EDT 
Created attachment 193708 [details]
Fix
Comment 3 Dani Megert CLA 2011-04-20 10:46:33 EDT 
Fixed in HEAD.
Available in builds >= N20110420-2000.