Bugzilla – Full Text Bug Listing
| Summary: | [javadoc wizard] Generating Javadoc for CUs with UTF-8 names fails on Windows | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> | ||||
| Component: | UI | Assignee: | Dani Megert <daniel_megert> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M7 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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. Created attachment 193708 [details]
Fix
Fixed in HEAD. Available in builds >= N20110420-2000. |
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.