@skabashnyuk It seems to be related with #12476, before that CORS on wsagent was a bit more liberal.
When running the normal setup on Docker (the one described on the wiki and in this issue) and accessing Che via http://localhost:8080 the following happens:
In CheWsAgentCorsAllowedOriginsProvider the value of apiExternal is equal to http://10.0.75.2:8080/api (or whatever ip the container has on the Docker NAT). This sets allowedOrigins to http://10.0.75.2:8080. This causes the wsagent server to not respond with any CORS headers when a request is sent from http://localhost:8080 or http://127.0.0.1:8080 because the host does not match.
I am currently not well known enough with the code to propose a proper solution for this.
代码补全快捷键 (Ctrl + Space) 不起作用
症状是报错与警告正常显示, 但在编辑器按快捷键 Ctrl + Space 尝试弹出代码补全的小框框时没有反应.
[ERROR] Found 1 non-complying files, failing build [ERROR] To fix formatting errors, run "mvn fmt:format" [ERROR] Non complying file:/home/xie/Workspace/Eclipse-Che/Eclipse-Che-6.16.0/instance/data/workspaces/workspaceo7zayfpxbzrdvmqf/che-test-extension/plugins/plugin-xxx/plugin-xxx-ide/src/main/java/zzz/yyy/ide/XXXExtension.java [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Plugin XXX :: Parent pom ........................... SUCCESS [ 1.921 s] [INFO] Plugin XXX :: Plugins :: Parent ................... SUCCESS [ 0.053 s] [INFO] Plugin XXX :: Plugin :: Parent ..................... SUCCESS [ 0.816 s] [INFO] Plugin XXX :: Plugin :: Server ..................... SUCCESS [ 3.759 s] [INFO] Plugin XXX :: Plugin :: IDE ........................ FAILURE [ 2.800 s] [INFO] Plugin xxx :: Che Assembly :: Assembly Parent ...... SKIPPED [INFO] Plugin XXX :: Che Assembly :: Workspace Agent Assembly SKIPPED [INFO] Plugin XXX :: Che Assembly :: Workspace Agent Tomcat Assembly SKIPPED [INFO] Plugin XXX :: Che Assembly :: IDE Assembly ......... SKIPPED [INFO] Plugin XXX :: Che Assembly :: Assemblies Tomcat .... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:11.225 s [INFO] Finished at:2019-07-08T10:26:53+08:00 [INFO] Final Memory:59M/1319M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.coveo:fmt-maven-plugin:2.5.1:check (default) on project plugin-xxx-ide: Found 1 non-complying files, failing build -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.coveo:fmt-maven-plugin:2.5.1:check (default) on project plugin-xxx-ide: Found 1 non-complying files, failing build at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
... ...
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :plugin-xxx-ide