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

Bug 334473

Summary:	doesn't load developing plug-ins when Japanese character is set on Run Configuration's Name
Product:	[Eclipse Project] PDE	Reporter:	Hiroki Kondo <kompiro>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer, ankur_sharma, curtis.windatt.public, harendra, tjwatson
Version:	3.7
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Hiroki Kondo

2011-01-16 01:44:29 EST

Build Identifier: M20100909-0800

It doesn't load the developing plug-ins on the launched eclipse environment when Run Configuration's name has some Japanese character.

Reproducible: Always

Steps to Reproduce:
1. create some plugin
2. open Run Configuration dialog
3. create new configuration and set 'あ' on Run Configuration's name
4. launch the configuration
5. check plug-in's list view and the created plugins are listed on the view.

Comment 1 Curtis Windatt

2011-01-19 17:43:14 EST

Tried this in linux and it works fine for me.

Can you please explain your problem in more detail.  Specifically, what do you mean by "5. check plug-in's list view and the created plugins are listed on the view."

Comment 2 Hiroki Kondo

2011-01-20 10:48:05 EST

Thanks for trying and sorry for my broken English.

I got the issue on MacOSX only.
I wanted to specify "5." is
"I can't load my workspace plugins on the launched workbench.(not hosted environment)."

Could you please check on the MacOSX?

Comment 3 Ankur Sharma

2011-01-21 04:07:05 EST

I was able to reproduce it on Mac OSX 10.6.5

If the launch config name is 'あ', then the workspace plug-in are not there in host eclipse (verified in Plug-ins and TPS view)

If the launch config name is in English characters, then the workspace plug-ins are visible and available.

Comment 4 Ankur Sharma

2011-01-24 03:25:16 EST

This is even worse on WinXp. Unable to launch only.

Comment 5 Ankur Sharma

2011-01-24 14:40:08 EST

(In reply to comment #4)
> This is even worse on WinXp. Unable to launch only.

The launch will work fine if the configuration location does not contains any non-ascii characters. The default configuration location can be overridden using Configuration tab -> configuration area -> uncheck default location

For comments on this behavior see Bug #159531

Comment 6 Ankur Sharma

2011-01-24 14:40:24 EST

Investigating for Mac now

Comment 7 Curtis Windatt

2011-01-24 16:03:56 EST

cc'ing Tom Watson

I know that DBCS and other character sets are not supported in bundle names, but is there an issue with one or more of these characters in the configuration area?

Comment 8 Thomas Watson

2011-01-24 17:19:07 EST

You need to check what characters are actually being read from the configuration properties for the osgi.configuration setting.

Add -console -noExit to the command arguments and then run the props command to see what the osgi.configuration value is set to.  My guess is that the encoding used to launch eclipse does not understand the characters and you will see '?' chars.

Comment 9 Ankur Sharma

2011-02-15 06:42:16 EST

Can you plz try with latest I-build and verify if you are still facing this problem? I am unable to reproduce the problem now. I am having 64 bit Java 1.6. I tried running it in both 32 and 64 bit modes and it was launching with workspace plug-ins. Also try once adding the Japanese language at System Preferences -> Language and Text -> Input sources.

When I launch I see this in the console 

Command-line arguments:  -product org.eclipse.sdk.ide -data /Users/ankur/pde/workspaces/workspace.36/../runtime-? -dev file:/Users/ankur/pde/workspaces/workspace.36/.metadata/.plugins/org.eclipse.pde.core/?/dev.properties -os macosx -ws cocoa -arch x86 -consoleLog


which verifies what Tom suggested.


If you are able to reproduce please add which JRE version you are using. Also do you see '?' characters.

Comment 10 Curtis Windatt

2011-02-28 12:59:21 EST

Needs input from the original bug reporter, removing milestone.

Comment 11 Hiroki Kondo

2011-03-01 08:42:51 EST

(In reply to comment #10)
> Needs input from the original bug reporter, removing milestone.

I'm the original reporter.
Unfortunately the bug is still occurred in Indigo M7 release.
(and I found new bug in the milestone release.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338530)

My tested version:
Version: Indigo Release
Build id: 20110204-0611
Eclipse RCP and RAP package

Comment 12 Curtis Windatt

2011-06-07 13:10:48 EDT

*** Bug 343226 has been marked as a duplicate of this bug. ***

Comment 13 Eclipse Genie

2019-09-16 12:35:26 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.