Focus on Java Projects View from command palette got a weird prefix

[jdneo]

And there is another problem: Focus on Java Projects View from command palette got a weird prefix as shown below:

if necessary, I would open a new issue for this, just let me know.

Originally posted by @Stargazer1209 in #846

[Stargazer1209]

Thank you, @jdneo , and I added some additional descriptions and log files below to help solve this problem.

1. the "focus on java project view" command would not appear in the command palette until I open some java source files or java project in the editor (I noticed that this is an expected behavior but maybe it has something to do with the problem).
2. And I just discovered that focus maven command also got this weird prefix with parts of it different from focus java project command's, as shown below.
   
3. Steps to reproduce:
   1. Launch vsocde from cli or with windows desktop shortcut using command "code.exe -profile 'java' "
   2. Open a local java maven project
   3. Wait for the status of java at the left bottom side of the screen change to "java: ready"
   4. Open command palette with "ctrl shift p" and search for "focus on java project/maven view"
   5. Then this weird prefix would show
4. Below is :

• vscode output from window channel
• vscode output from extension host channel
• vscode output from main process channel

note that I am using vscode with Chinese Simplified language extension, so the above channel name (translated by me) may be different from what they actually are

• vscode profile in the scenario exported
  window channel output.txt
  extension host channel output.txt
  main process channel output.txt
  java.code-profile.txt

[jdneo]

Hi @Stargazer1209

I was just about to create an issue for this problem in VS Code repo, then I found that this issue can be reproduced in VS Code stable. But when I use latest VS Code Insiders, the command name looks fine.

Is it the same on your side as well?

[jdneo]

Yes I think it's this one: microsoft/vscode#201085

Highly likely it's already fixed from VS Code side.

[Stargazer1209]

Yes I think it's this one: microsoft/vscode#201085

Highly likely it's already fixed from VS Code side.

Yes, the same from my side, it works fine with insider version. Hope we can get this fix soon in stable release.

[jdneo]

Close as it's fixed from upstream.