You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple of issues related to che-in-che(6) that cannot be solved simple on the Che side. Currently, the approach in VSCode-Java is to assume that the projects in the "workspace" are static, in particular, no new projects are detected if they are added to an open folder in the workspace (see also #144).
In Che6, importing new projects into "the workspace" is a common occurrence. The test case in question is importing the source code from https://github.com/eclipse/che into a workspace. This takes a long time and the workspace does not provide Java related functionality until the initialization phase is over. There are a couple of things we could do to improve things, in particular:
There are a couple of issues related to che-in-che(6) that cannot be solved simple on the Che side. Currently, the approach in VSCode-Java is to assume that the projects in the "workspace" are static, in particular, no new projects are detected if they are added to an open folder in the workspace (see also #144).
In Che6, importing new projects into "the workspace" is a common occurrence. The test case in question is importing the source code from https://github.com/eclipse/che into a workspace. This takes a long time and the workspace does not provide Java related functionality until the initialization phase is over. There are a couple of things we could do to improve things, in particular:
The text was updated successfully, but these errors were encountered: