-
Notifications
You must be signed in to change notification settings - Fork 44
Codewind no longer auto-detect appsody project #445
Codewind no longer auto-detect appsody project #445
Comments
I'm looking into this |
Sure. It would be possible to fix this through the Appsody logic in the CLI but your solution is much cleaner for the long term. |
Looks like appsody project imports are failing to set language type intermittently even though I selected language type "Java". Steps to recreate.
This happens 50% of the time and this is intermittent. We see mixed results. You can see the screenshot below, the image for Java project is not for Java and language is set "Unknown" in overview page. This seems to be regression and we need to deliver the fix for this as we have conferences scheduled in the coming weeks. |
The language select problem is likely not directly caused by this issue (not auto-detecting appsody project) but it is exposed by it (since now you always have to choose the type and language when importing an appsody project) The language select problem is possibly fixed by eclipse-archived/codewind-eclipse#309; @eharris369 can confirm. And looks like the related fix on vscode side is eclipse-archived/codewind-vscode#208 |
The language issue will be fixed by eclipse-archived/codewind-eclipse#309. Just waiting for John to review. |
Codewind version: 0.4.0
OS:
Che version:
IDE extension version:
IDE version:
Kubernetes cluster:
Description:
I believe when we switched over to using installer CLI for project validation and creation, we are no longer able to auto-detect an appsody project, as evident by the following test:
Note the
"projectType": "docker"
in the response. As a result, when we import an existing appsody project into IDEs, user will always get prompted to pick the project type.Steps to reproduce:
Workaround:
The text was updated successfully, but these errors were encountered: