`./mvnw quarkus:dev` and VSCODE Java build seem to interfere

[col-panic]

I want to debug the quarkus application using the internal debugger

First to have a clean workspace I press the Rebuild All

and every class seems good. All of them are either yellow or green.

Now I start via Debug quarkus:dev (server) in launch.json, running ./mvnw quarkus:dev -Dliquibase.secureParsing=false from tasks.json (see enclosed) maven starts and suddenly the building starts again

After quarkus:dev reached its final state, I have lots of build errors

and vscode complaining about corrupt classes

It seems somehow that vscode and the commandline tool seem to interfere and each doing its own imcompatible build!

What is wrong here? What do I need to change??

launch.json
tasks.json

[rgrunber]

I don't think they should interfere when runnnig quarkus:dev. At least when I take a simple quarkus project and run quarkus:dev I don't see any indication that it triggered a rebuild. I have seen this before though with other projects (eg. mvnw clean verify). One workaround is to maybe try disabling the autobuild to see if it still occurs ( "java.autobuild.enabled": false) ? Likely the commandline build is modifying files, that are being watched by either vscode-java/vscode-quarkus, and for some reason that triggers a rebuild. However both processes (mvnw cli vs. vscode) may be writing out their content to the output locations causing some unexpected behaviour. I've gotten ClassNotFoundExceptions in the past when calling mvn from cli while having the same file open in an IDE.

@col-panic would you be able to set "java.trace.server": "verbose" and when this issue occurs can you send the log files shown by Java: Open All Log Files (ideally there should be a .log and client.log). What I'm interesting in is specifically after you run the mvnw quarkus:dev call (ie. through the launch entry), what is the language server requesting be watched (in the logs) :

[Trace - 15:27:20] Sending notification 'workspace/didChangeWatchedFiles'.
Params: {
    "changes": [
        {
            "uri": "...",
            "type": ...
        }
    ]
}

This might give a hint as to what files are causing the build to retrigger. In fact if you see progress notifications after that relating to build, that would be a good indicator.

[col-panic]

Hey @rgrunber I tried doing it as you described, I hope its ok like that. I did some additional remarks in the .log file to pinpoint the actions like !! NOW RUNNING DEBUG QUARKUS:DEV

.log

Archiv.zip

[rgrunber]

So when you initially call the projet build just before 16:40:01.885 I can see in the client logs that corresonds to :

{ 
  message: "[Trace - 16:40:00] Sending request 'java/buildWorkspace - (20)'.",  level: 'info',
  timestamp: '2025-04-11 16:40:00.444'
}

I can also see after that :

{
  message: "[Trace - 16:40:02] Sending notification 'workspace/didChangeWatchedFiles'.",
  level: 'info',   
  timestamp: '2025-04-11 16:40:02.720'
}   
{   
  message: 'Params: {
        "changes": [
            {
                "uri": "file:///Users/mdescher/git/myelexis-server/entities/target/generated-sources/annotations/ch/myelexis/jpa/entities/AUF_.java",\n' +
                "type": 1
            }
            ...
            ...
        ]   
}

So you your build has some instructions to generate some source files as a step likely before compilation.

When you perform the ./mvnw quarkus:dev from the CLI, you mention you do it just before 16:40:53.665.

That would correspond with :

{
  message: 'No result returned.\n\n',
  level: 'info',
  timestamp: '2025-04-11 16:40:31.059'
}
{
  message: "[Trace - 16:40:52] Sending notification 'workspace/didChangeWatchedFiles'.",
  level: 'info',
  timestamp: '2025-04-11 16:40:52.324'
}
{
  message: 'Params: {
        "changes": [
            {
                "uri": "file:///Users/mdescher/git/myelexis-server/entities/target/generated-sources/annotations/ch/myelexis/jpa/entities/Labor2009Tarif_.java",
                "type": 1
            }
            ...
            ...
        ]
}

And further down :

{
  message: 'Params: {
        "token": "965b061d-ad3e-4704-8aa4-adece8bbda8b",
        "value": {
            "kind": "begin",
            "title": "Building",
            "message": "Building"
        }
    }
  level: 'info',
  timestamp: '2025-04-11 16:40:56.923'
}

So it definitely looks like the CLI call, which would probably regnerate the source files is causing the language server to perform a rebuild. @col-panic Does just disabling the autobuild ("java.autobuild.enabled": false) work ? I mean if you have the Maven quarkus:dev task listening for changes, or are always running it, you probably don't need vscode-java to perform the builds.

[col-panic]

So you your build has some instructions to generate some source files as a step likely before compilation.

Oh, that makes sense now, this is the model generator for the hibernate plugin. It generates the meta model for the entity classes.

 <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <annotationProcessorPaths>
                        <path>
                            <groupId>org.hibernate.orm</groupId>
                            <artifactId>hibernate-jpamodelgen</artifactId>
                        </path>
                    </annotationProcessorPaths>
                </configuration>
            </plugin>

I tried java.autobuild.enabled once and things seemed to go better! I had it complaining now once about some problems in pom.xml but generally it seems much more stable and it also connects to the vscode debugger!

[rgrunber]

We've also identified some possible performance issues with the autobuilder that would affect Quarkus projects. Will have to investigate more closely into M2E.

Update: I think it's worth filing a separate issue for this. I've created #1004 .