The bug is relevant for eclipse/che-theia:next, so for master branch assembly.
After alignment theia tasks with vs code behavior we need some adaptation on our side.
I still can run che tasks, but at least:
Terminal -> Run Task menu action is triggered only on second clickI tested it on theia side and it works well.
Looks like some changes for task definitions are required on our side.
-
alias: theia-editor
reference: >-
https://raw.githubusercontent.com/eclipse/che-plugin-registry/master/v3/plugins/eclipse/che-theia/next/meta.yaml
type: cheEditor
detected tasks the type of the task is used, not source (for example, shell instead of npm )detected task - click on cog icon - the configuration should be copied to tasks.json file, but nothing is happen.detected taskssource field is used for displaying of detected tasksTerminal -> Run Task menu action is triggered on first click kubectl version) oc version)minishift version and oc version)docker version and kubectl version)Actual displaying

Expected displaying

cc @slemeur I think we need to take it for 7.1
WDYT?
@slemeur moved to 7.1.0 for now
I added to the description of the issue one more use case related to Terminal -> Run Task menu.
The video for the case is available as well.
The bug was caused by last changes in master branch of theia repo. I can not reproduce it for theia project, so some changes are required on che-theia side.
I investigated the issue: the bugs related to detected tasks are caused by using 7.0.0-next version of eclipse/che-theia-endpoint-runtime for remote plugins. 7.0.0-next version doesn't contain activateByEvent logic.
So the issue is fixed by using next version of eclipse/che-theia-endpoint-runtime for remote plugins.
Most helpful comment
@slemeur moved to
7.1.0for now