Tasks of remote plugins are not redirected to corresponding container

[RomanNikitenko]

Description

We have remotes plugins. I turned on the typescript plugin for my workspace and tried to run 'build' and 'watch' tasks for che-theia project, but they failed.
ProcessTaskRunner is used for running typescript task configurations, so tasks for remote plugins are not redirected to container of the plugin at the moment.

Reproduction Steps

1. Create workspace using Che 7 Theia dev stack
2. Turned on typescript plugin
3. Start workspace and clone che-theia project
4. Run 'detected' 'build' or 'watch' task using 'Terminal' => 'Run Tasks' menu

[tsmaeder]

So which container are the tasks executed in and which container would you expect them to be executed in?

[RomanNikitenko]

Tasks provided by remote plugins are executed in theia-ide container. I expect that they should be executed in a plugin container.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[RomanNikitenko]

/remove-lifecycle stale

[tsmaeder]

@ericwill this is one of the more serious problems we have mapping VS Code stuff to our workspace model: where do we run things like tasks, etc.
In the end, we can't know where to run tasks: for example, we might want to run a maven build on the dev machine, not the java plugin sidecar. I believe we should implement two things:

1. Extend the theia task system to include a "target component" for every task. This will be a complicated undertaking
2. Allow for che plugins to annotate the tasks contributed by vs code extensions with a hint where they should run.

[ericwill]

@ericwill this is one of the more serious problems we have mapping VS Code stuff to our workspace model: where do we run things like tasks, etc.
In the end, we can't know where to run tasks: for example, we might want to run a maven build on the dev machine, not the java plugin sidecar. I believe we should implement two things:

1. Extend the theia task system to include a "target component" for every task. This will be a complicated undertaking

2. Allow for che plugins to annotate the tasks contributed by vs code extensions with a hint where they should run.

Thanks for the context, we should probably provide this feature sometime soon-ish.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.