Openshift connector and Che: not possible to have 2 components connected to 2 projects in the same workspace

[sunix]

Describe the bug

With the openshift connector, trying to create 2 components linked to 2 projects in the same workspace. Openshift connector is trying to open a new workspace (window) for each component. but somehow, Che is not handling that situation well: some views are broken and the user may want to stay in a single window.

[tsmaeder]

Upstream issue?

[sunix]

@tsmaeder this is a high level user issue, the assignee who would take it would analyse a create upstream issue if needed.

[azatsarynnyy]

@sunix could you please describe in detail what are the steps to reproduce the described bug.

I've been able to successfully create two components linked to two different projects.
See it in my last demo https://www.youtube.com/watch?v=kjVBLqTNvRA

[sunix]

@azatsarynnyy it is because your are using a binary file for the backend. it fails with 2 components using both source folders in the same workspace.
I am making more tests at the moment to provide more information but the problem may come by the fact that the vscode openshift connector works well with workspace root for each component

[sunix]

@azatsarynnyy to me this is the right way to fix this issue: #15347
I have tried to manually add workspace roots for each components and it works well.

[azatsarynnyy]

@sunix I see. Thank you for the explanation!

[sunix]

@azatsarynnyy having that said, I think we should have a better way to manage workspace roots in general: when a plugin/vscode ext is trying to open a new workspace of a specific folder, we should add a workspace root instead in the current workspace. WDYT ?

[azatsarynnyy]

I like the solution proposed in #15347

[azatsarynnyy]

relabeled to area/plugins as it's related to OpenShift Connector plugin

[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.