Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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. #3838

Open
mozhuanzuojing opened this issue Nov 1, 2024 · 0 comments

Comments

@mozhuanzuojing
Copy link

mozhuanzuojing commented Nov 1, 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

  1. git clone https://gitee.com/mozhuanzuojing/bug02.git
  2. open bug02 and wait java status Ready
  3. exec ./mvnw clean package
  4. watch PROBLEMS output

Image

@mozhuanzuojing 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant