Community
Participate
Working Groups
Language: Simplified Chinese OS: Windows 2000 Eclipse Build: 200302061700 Stable Build (M5) JRE version: JRE 1.4.0 IBM build cxia32140-20020917a (JIT enabled:jitc) <<Summary>> Cannot export package with GB18030 chars as package name to a Javadoc <<Re-produce steps>> 1. Launch Eclipse. 2. Create a Java project with GB2312 chars as project name. 3. Create a Java package with GB18030 chars as package name. 4. Create two Java classes, put one in the new package and the other in the default package. 5. Right click the project and click Export. 6. Select Javadoc and click Next button. 7. Click Finish button. <<Expected Result>> It works correctly <<Execution Result>> Error message displays in the console, please refer to screen shot =>javadoc1.jpg <<Comments>> 1. I can run it with GB2312 character. 2. I have change the Fonts for workbench and system to GB18030 character. 3. It seems that source files cannot be found in the package with GB18030 chars as package name.
Created attachment 3565 [details] Screen shot of javadoc1.jpg
The actual Javadoc generation is done by calling the javadoc executable from a JDK installation. Which version of javadoc are you using (Preferences->Java- >Javadoc). The error messages you are seeing in the output window are generated by the javadoc executable not by Eclipse itself. Would it be possible that you translate the error message ;-)).
I tested it under Windows 2000 with Simpified Chinese and the Javadoc wizard passes the following arguments to the javadoc exe D:\apps\jdk\jdk1.4.1\bin\javadoc.exe -d C:\tmp\JUnit\成\doc -sourcepath C:\tmp\JUnit\成 -classpath C:\tmp\JUnit\成 -public -use -version -author - splitindex C:\tmp\JUnit\成\成.java 在 IMO the -locale and -encoding arguments are missing. Martin, any comments
Dirk, answer your questions: 1. JDK version we are using: build 1.4.0, J2RE 1.4.0 IBM Windows 32 build cn140-20020902 (JIT enabled: jitc) 2. Translate the error message: "javadoc: no found source file in the package ??"
There is an old PR saying that there are problems to pass chinese charaters to a second process. Have to find PR.
This seems to be a more fundamental problem of the VM. Trying to start a VM where the main class name uses GB1830 characters results in the following error message: The java class is not found: ? The command used to start the VM is D:\apps\jdk\1.4.0_IBM\jre\bin\javaw.exe -classpath C:\tmp\workspaces\Chinese\Test 成 The VM used is java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902 (JIT disabled) BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US According to bug 9330 this seems to be a VM bug. Since the Javadoc exec is a Java VM too it will surface the same behavior. Creating Javadoc for files which use DBCS for the content works as long as the right encoding is specified using the additional field "Extra Javadoc options" on the wizard's third page (e.g entering -encoding UTF-16). As long as the VM problem exists there is nothing we can do. Removing milestone tag. Asking JDT/Debug if they have more insights about this ?
We have a similar bug filed against us, which is still under investigation - bug 32206.
With RC1 I just restested this using the following parameters VM: IBM 1.4.0 Sept 17 build. Input mode:Nei Ma Unicode Locale: zh_CW Encoding: GB18030 I created a project, class and package using the Unicode input and then generated javadoc and did not guess this problem. I am not sure if this indicates that the problem is fixed - could Yu Zhen Fan please verify my test methods. If they are invalid please let me know how you inputted the proglem characters.
With RC1 I just restested this using the following parameters: VM: IBM 1.4.0 Sept 17 build. Input mode: Nei Ma Unicode Locale: zh_CN Encoding: GB18030 Characters: 3400 - 3700 range (difference between reporter and Tod Creasey) We can still make this problem happen. Please input Unicode like "3400" for retesting. For more comments, refer to bug 32206.
I have done the same test abd also got an error but this time I got an internal error !ENTRY org.eclipse.jdt.ui 4 10001 ÈýÔÂ 11, 2003 02:29:58.80 !MESSAGE Internal ErrorÎÄ* !STACK 0 java.io.IOException: CreateProcess: D:\½¢ꤰ½¢\ibmjre\bin\javadoc.exe -d D:\tod\RC2\eclipse\workspace\㑖´K\doc -sourcepath D:\tod\RC2 \eclipse\workspace\㑖´K -classpath D:\tod\RC2\eclipse\workspace\㑖´K -public - use -version -author -splitindex 㑖㙸 error=123 at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Win32Process.java:91) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:583) at java.lang.Runtime.exec(Runtime.java:505) at java.lang.Runtime.exec(Runtime.java:471) at org.eclipse.jdt.internal.ui.javadocexport.JavadocWizard.executeJavadocGeneratio n(JavadocWizard.java:221) at org.eclipse.jdt.internal.ui.javadocexport.JavadocWizard.performFinish (JavadocWizard.java:179) at org.eclipse.jface.wizard.WizardDialog.finishPressed (WizardDialog.java:602) at org.eclipse.jface.wizard.WizardDialog.buttonPressed (WizardDialog.java:315) at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:417) at org.eclipse.swt.widgets.TypedListener.handleEvent (TypedListener.java(Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code)) at org.eclipse.jface.window.Window.open(Window.java:557) at org.eclipse.ui.actions.ExportResourcesAction.run (ExportResourcesAction.java:112) at org.eclipse.jface.action.Action.runWithEvent(Action.java:842) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:456) at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent (ActionContributionItem.java:403) at org.eclipse.jface.action.ActionContributionItem.access$0 (ActionContributionItem.java:397) at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent (ActionContributionItem.java:72) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1383) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:845) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:61) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:40) at java.lang.reflect.Method.invoke(Method.java:335) at org.eclipse.core.launcher.Main.basicRun(Main.java:247) at org.eclipse.core.launcher.Main.run(Main.java:703) at org.eclipse.core.launcher.Main.main(Main.java:539)
The analysis we have done indicates that the class libraries do not support the creation of a process via Runtime.exec(...). See bug 32206 for more details.
