Bug 223177 - [javadoc export] {bidi] BIDI3.4:HCG JavaDoc generation fails if Hebrew data is involved
Summary: [javadoc export] {bidi] BIDI3.4:HCG JavaDoc generation fails if Hebrew data i...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2008-03-19 06:12 EDT by Ira Fishbein CLA
Modified: 2008-04-08 10:23 EDT (History)
5 users (show)

See Also:


Attachments
Java project with Hebrew data for import (2.60 KB, application/octet-stream)
2008-03-19 06:12 EDT, Ira Fishbein CLA
no flags Details
Console screenshot with errors (132.72 KB, image/jpeg)
2008-03-19 06:13 EDT, Ira Fishbein CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ira Fishbein CLA 2008-03-19 06:12:58 EDT
Created attachment 92879 [details]
Java project with Hebrew data for import

Build ID: IES3.4 B20080207-1530
Platform: MAC OS X 10.5

1. Generate Java project with Hebrew data involved (you can import java project from attached zip, you should use UTF-8 encoding)
2. Try to generate JavaDoc (Project->Generate Javadoc menu)
Result: JavaDoc generation fails (attached screenshot with Console errors)
Comment 1 Ira Fishbein CLA 2008-03-19 06:13:56 EDT
Created attachment 92880 [details]
Console screenshot with errors
Comment 2 Martin Aeschlimann CLA 2008-03-19 20:49:10 EDT
That's a problem of the Javadoc command. Nothing we can do there.
Comment 3 Ira Fishbein CLA 2008-03-20 07:46:43 EDT
From what I see, there is parameter called 'encoding' that can be passed to javadoc.exe in command line. It looks like Eclipse doesn't allow passing this parameter.
Comment 4 Ira Fishbein CLA 2008-03-20 07:47:32 EDT
reopening the bug
Comment 5 Martin Aeschlimann CLA 2008-03-20 17:23:14 EDT
You can specify extra programm and VM arguments on the last page of the Javadoc wizard. Can you try this?
Comment 6 Dani Megert CLA 2008-03-21 03:09:20 EDT
Yes, this will most likely "fix" it but the point is that we know the project encoding already. Of course it gets messy when people use different encodings per folder or even per file.
Comment 7 Ahmed Farrag CLA 2008-04-02 10:09:15 EDT
Bidi team in Egypt also encountered this problem when Arabic data exists inside the code. However, passing the "-encoding UTF8" parameter on the last page of the Javadoc wizard has resolved this problem.
Comment 8 Ahmed Farrag CLA 2008-04-02 10:25:17 EDT
I would suggest to mark this bug as resolved and add remark to eclipse release note regarding this issue and how to resolve.
Comment 9 Martin Aeschlimann CLA 2008-04-08 10:23:58 EDT
Will add a note to documentation