Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to install Theia Plugins

See original GitHub issue

Description

It looks after merging the PR installing of Theia Plugins become impossible. All Theia plugins configured in workspace config are handled as VS Code extensions and downloaded in /plugins directory with wrong extension.

Screenshot below displays logs of plugin broker while installing the plugins Screenshot from 2019-05-16 16-57-46

A plugin eclipse-che/tree-view-sample-plugin/0.0.1 is a Theia plugin temporary stored on github in https://raw.githubusercontent.com/vitaliy-guliy/che-theia-plugin-registry/master/plugins/eclipse-che/tree-view-sample-plugin/0.0.1/meta.yaml

I opened terminal for theia-ide container and listed /plugins directory Screenshot from 2019-05-16 17-40-40

Blocks https://github.com/eclipse/che/issues/12905

Reproduction Steps

Install che-omnisharp-plugin plugin got from plugin registry by adding redhat-developer/che-omnisharp-plugin/0.0.1 to workspace configuration
install custom tree-view-sample-plugin plugin built from che-theia-samples by adding https://raw.githubusercontent.com/vitaliy-guliy/che-theia-plugin-registry/master/plugins/eclipse-che/tree-view-sample-plugin/0.0.1 to workspace configuratoin

OS and version:

Diagnostics:

Issue Analytics

State:
Created 4 years ago
Comments:11 (9 by maintainers)

Top GitHub Comments

2reactions

amisevskcommented, May 29, 2019

@makandre Yes, the “magically” part is the versioning for the plugin broker.

On Che, you are likely using plugin broker v0.17, which automatically takes bugfix releases – I just released v0.17.2 including David’s fix (which was merged a bit ago but I forgot to make a release out of it).

The reason the filename in the filesystem is strange is mostly to avoid name collisions – it shouldn’t interfere with functionality. The reasoning behind it is that a single plugin could define multiple extensions, so the naming scheme is required. The reason you’re seeing <my_theia_plugin> twice is because for theia plugins we try to append the original filename (to keep the extension).

0reactions

makandrecommented, May 30, 2019

… now magically it started to work 😃 I guess some backend processes finally kicked in?

I do still see Downloading VS Code extension for plugin 'my-theia-plugin tho.

On the fs, the filename looks like <my-theia-plugin>.<version>.<random-chars>.<my_theia_plugin>.theia

Top Results From Across the Web

Cannot automatically install vscode plugin in Theia

I just found my answer, I can use the THEIA_PLUGINS environment variable to set the plugins folder: THEIA_PLUGINS=local-dir:./plugins yarn start ...

How to add extensions and plugins to Eclipse Theia

This article describes how to add extensions and plugins to the Eclipse Theia IDE, during development time and during runtime.

@theia/plugin-ext - npm

The @theia/plugin-ext extension contributes functionality for the plugin API. Implementation. The implementation is inspired from: https://blog.

Add VSXI plugin to Eclipse Theia | It's full of stars!

Download the VSIX file from GitHub (when I wrote this: v1.7.7). Add it to Eclipse Theia. For this, use the command “Extensions: Install...

Recently Active 'theia' Questions - Stack Overflow

I am working on an plugin system like https://github.com/eclipse-theia/theia/blob/master ... Unable to install vscode-ripgrep on Docker: Unexpected token ".