Java plugin rebuilds project code everytime i instruct maven to compile

[palminha]

I have a java/maven/spring project.

The IDE is showing the JAVA build option in the bottom bar... it seems it using the JAVA plugin to build the project

when i try to build my project using maven, the JAVA tries to rebuild in parallel and i get a lot of problems with the compilation

[rgrunber]

What happens if you add the setting "java.autobuild.enabled": false ? Does that solve the build issues ? It might be that your Maven build makes certain modifications that cause the Java support to detect certain changes that then trigger the autobuild. With this setting you would have to manually trigger the rebuild but may be worth it if it solves the conflict.

[palminha]

What happens if you add the setting "java.autobuild.enabled": false ? Does that solve the build issues ? It might be that your Maven build makes certain modifications that cause the Java support to detect certain changes that then trigger the autobuild. With this setting you would have to manually trigger the rebuild but may be worth it if it solves the conflict.

@rgrunber, that's a good mitigation, thanks. However, I won't be able to access the "problems" tab, or other functional features, that it seems it requires the java plugin...

Returning to my original point: resolve the issue with Maven-Java not functioning correctly.

[palminha]

"java.autobuild.enabled": false doesn't block the code to be built by java plugin when i open vscode

[rgrunber]

What do you mean by accessing the problems tab ? Even if you disabled auto-build, you can still manually call Java: Rebuild Projects or Java: Force Java Compilation to have the problems view populated with issues. Is that what you meant ?

[palminha]

What do you mean by accessing the problems tab ? Even if you disabled auto-build, you can still manually call Java: Rebuild Projects or Java: Force Java Compilation to have the problems view populated with issues. Is that what you meant ?

If i turn "java.autobuild.enabled": false and build the project using maven (manually select it), the problems view is not populated with results

[rgrunber]

Would you be able to share the project ? Even if you could only share the project without the sources, and could mention the kind of problems that don't get reflected in the problems view, would help.

[palminha]

Would you be able to share the project ? Even if you could only share the project without the sources, and could mention the kind of problems that don't get reflected in the problems view, would help.

@rgrunber thanks for following up... I have open a separate topic about that specific issue: #4117

[rgrunber]

If this particular issue now remains about a conflict between the Java VS Code extension and the calling of a build tool from commandline (or some other way), then this seems very similar to redhat-developer/vscode-quarkus#999 . That one was about using the Quarkus tooling & Java extension ,but the idea is the same. Running a build command (even within the terminal of VS Code) while the Java extension is set to autobuild can cause conflicts.