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

Bug 343226

Summary: DBCS4.1: Cannot create plugins with DBCS plugin project name.
Product: [Eclipse Project] PDE Reporter: Harendra <harendra>
Component: UIAssignee: Ankur Sharma <ankur_sharma>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, kennoji, kitlo, namle, pwebster
Version: 4.0   
Target Milestone: 3.8   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Harendra CLA 2011-04-19 01:18:40 EDT
Build Identifier: I20110412-2200


OS: Mac OS X
Java environment:1.6.0_24-b07-334
Locale:ja_JP.UTF-8

Reproducible: Always

Steps to Reproduce:
1.Create a new plugin project with project name プラグイン
2.Choose plugin with a view and click finish.
3.Run the plugin as Eclipse Application, the Sample View will not be present under
   the list of view. (i.e Window->Show View->others)
It is same for other sample plugins too.
Comment 1 Curtis Windatt CLA 2011-05-06 15:44:14 EDT
I haven't been able to reproduce, I installed the japanese language pack from Babel and launched with the ja_JP locale.  All the sample views show up correctly.  If the views are not available in the runtime workbench, I suspect there is a configuration problem with the plug-in in the host or the launch config.
Comment 2 Ankur Sharma CLA 2011-05-11 16:36:01 EDT
This could be related to Bug #334473.

The view is not available because the plug-in didn't load. I get this exception when I open Plug-ins view. This indicates that the plug-in probably didnt load because some URI failed somewhere. Investigating.

eclipse.buildId=I20110509-1200
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20080811 (JIT enabled)
J9VM - 20080809_21892_lHdSMr
JIT  - 20080620_1845_r8
GC   - 200806_19
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.sdk.ide
Command-line arguments:  -product org.eclipse.sdk.ide -data C:\PDE\workspaces\workspace.test/../runtime-EclipseApplication -dev file:C:/PDE/workspaces/workspace.test/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86 -consoleLog

Error
Thu May 12 02:02:15 IST 2011
Unable to create view ID org.eclipse.pde.ui.PluginsView: Plug-in "org.eclipse.pde.ui" was unable to instantiate class "org.eclipse.pde.internal.ui.views.plugins.PluginsView".

java.lang.IllegalArgumentException: URI has a query component
	at java.io.File.<init>(File.java:371)
	at org.eclipse.pde.internal.core.P2Utils.copyURLs(P2Utils.java:167)
	at org.eclipse.pde.internal.core.P2Utils.readBundlesTxt(P2Utils.java:80)
	at org.eclipse.pde.internal.core.PluginPathFinder.getPluginPaths(PluginPathFinder.java:101)
	at org.eclipse.pde.internal.core.ExternalModelManager.getPluginPaths(ExternalModelManager.java:99)
	at org.eclipse.pde.internal.core.PluginModelManager.initializeTable(PluginModelManager.java:512)
	at org.eclipse.pde.internal.core.PluginModelManager.getState(PluginModelManager.java:1053)
	at org.eclipse.pde.internal.core.TargetPlatformHelper.getPDEState(TargetPlatformHelper.java:425)
	at org.eclipse.pde.internal.ui.util.SourcePluginFilter.<init>(SourcePluginFilter.java:28)
	at org.eclipse.pde.internal.ui.views.plugins.PluginsView.<init>(PluginsView.java:81)
	at java.lang.Class.newInstanceImpl(Native Method)
	at java.lang.Class.newInstance(Class.java:1328)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
	at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:260)
	at org.eclipse.ui.internal.registry.ViewDescriptor.createView(ViewDescriptor.java:63)
	at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:327)
	at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
	at org.eclipse.ui.internal.Perspective.showView(Perspective.java:2245)
	at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1145)
	at org.eclipse.ui.internal.WorkbenchPage$20.run(WorkbenchPage.java:3921)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3918)
	at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:94)
	at org.eclipse.ui.internal.quickaccess.QuickAccessDialog.handleElementSelected(QuickAccessDialog.java:724)
	at org.eclipse.ui.internal.quickaccess.QuickAccessDialog.handleSelection(QuickAccessDialog.java:801)
	at org.eclipse.ui.internal.quickaccess.QuickAccessDialog.access$6(QuickAccessDialog.java:791)
	at org.eclipse.ui.internal.quickaccess.QuickAccessDialog$10.widgetDefaultSelected(QuickAccessDialog.java:330)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:119)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4163)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:618)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Comment 3 Harendra CLA 2011-05-11 22:18:27 EDT
(In reply to comment #1)
> I haven't been able to reproduce, I installed the japanese language pack from
> Babel and launched with the ja_JP locale.  All the sample views show up
> correctly.  If the views are not available in the runtime workbench, I suspect
> there is a configuration problem with the plug-in in the host or the launch
> config.
Can you please write down the exact steps you followed.
Comment 4 Ankur Sharma CLA 2011-05-18 15:45:33 EDT
@Harendra
does your launch configuration name and/or launch runtime workspace contains Japanese characters? Please try launching using a config that has all ascii name and workspace path

in my opinion this bug is probably same as 334473

that is, if the launch config name or workspace contains dbcs characters, we can not launch properly (due to command line limitations)


I recommend we take it off 3.7 radar
Comment 5 Harendra CLA 2011-05-18 21:35:07 EDT
Yes the plugin project name is in Japanese.
Comment 6 Curtis Windatt CLA 2011-06-07 13:10:48 EDT

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