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
After the maven is packaged, the java file generated in the output directory target is re-recognized as a project file by the vscode-java plugin, and then a lot of diagnostic information is sent. (until the file becomes normal after opening the file in vscode (recompiling again)).
Because these java source files are compiled in the vscode-java plugin, the source code and dependencies of the module in which they are located are not added, resulting in a compilation error that does not recognize import class of module.
The text was updated successfully, but these errors were encountered:
mozhuanzuojing
changed the title
After the maven is packaged, the java file generated in the output directory target is re-identified as a project file by the vscode-java plugin.
After ./mvnw clean package, the java file generated in the output directory target is re-identified as a project file by the vscode-java plugin.
Nov 2, 2024
After the maven is packaged, the java file generated in the output directory target is re-recognized as a project file by the vscode-java plugin, and then a lot of diagnostic information is sent. (until the file becomes normal after opening the file in vscode (recompiling again)).
Because these java source files are compiled in the vscode-java plugin, the source code and dependencies of the module in which they are located are not added, resulting in a compilation error that does not recognize import class of module.
step
./mvnw clean package
PROBLEMS
outputThe text was updated successfully, but these errors were encountered: