-
Notifications
You must be signed in to change notification settings - Fork 44
SVT: Missing files error when importing some Appsody projects (VS code) #488
Comments
This is basically same as #445 (for which there is a PR to fix: eclipse-archived/codewind-installer#126) |
The vs code behaviour is correct; portal is providing bad info, and the user will likely not know better than to override it (by selecting "No, this is not the correct type" and then selecting Appsody) |
eclipse-archived/codewind#488 Signed-off-by: Tim Etchells <[email protected]>
eclipse-archived/codewind#488 Signed-off-by: Tim Etchells <[email protected]>
I tested this problem on 2019-09-19. Users may not encounter this problem frequently, as Appsody projects are now being detected correctly. However, if the user selects "No" in the confirmation window and then enters the same type and language, he/she will get the error presented above regarding the missing files. For example, if the project type appears in the confirmation window as "appsodyExtension" and the project language as "java", and you enter the exact information manually, you will get the missing files error. |
@tetchel there were some language selection bug in IDE that was fixed I believe? |
yes, that was #486 - this new issue is separate, for if the user chooses to ignore the autodetection even though it is correct. |
I expect it has something to do with the installer tracking |
|
ok, if this behaviour is changing in 0.5 i think we should consider this issue good for now (since it doesn't make much sense for a user to ignore the correct autodetection), and verify the new behaviour when it's in? |
This has been fixed for a while. Can we close? |
Codewind version: 0.4.0
OS: Windows 10 and MacOS Mojave (10.14.6)
IDE extension version: 0.4.0
IDE version: 1.38.1
Description: In VS Code, users are requested to confirm the type and language of the project to be imported. However, the types are always incorrect and if the user selects “yes”, the import will fail due to missing files. This error occurs with all Appsody projects, except Appsody Eclipse MicroProfile and Appsody Python Flask. These latest templates currently do not automatically detect any information from the imported project.
Steps:
Workaround: Manually change the project type to appsodyExtension.
@jagraj
The text was updated successfully, but these errors were encountered: