Marco Collovati

There is a mention of this situation in the [Troubleshooting](https://vaadin.com/docs/latest/production/troubleshooting#flow-build-info-json-file) section of the documentation.

> Seems like many of the errors are related to `mvn compile` running `mvn vaadin:prepare-frontend` which apparently always writes new versions of all files The first action that `vaadin:prepare-frontend` performs...

Another cause is that, when maven build executes prepare-frontend, the `vaadin-dev-server-settings.json` is overwritten with different contents, triggering another Vite restart. This is the content generated by the application at first...

Another cause of restart is `flow-build-info.json` that is always updated, even if there are no changes.

Another case for restart related to `flow-build-info.json`: if the application is started from the IDE it will not create a `flow-build-info.json` file, so when `prepare-frontend` is executed, it will create...

With the changes from the linked PRs, I get a single restart because of class changes ``` 2024-03-22T08:36:09.326+01:00 INFO 20617 --- [ File Watcher] rtingClassPathChangeChangedEventListener : Restarting due to 4...

Delete was introduced by #16647 to fix #16640. It seems to me it could be still relevant

Most of the restart causes should have been fixed. I plan to retest today.

Tested against beta2 and I can see a single restart after compiling changes. I also tried it with the Gradle starter project, by having one terminal running `./gradlew bootJar` and...

Can we also prevent running `TaskGenerateEndpoint` if there are no endpoint annotated classes? (I mean when potential Hilla views are detected, but there are no endpoint implementations)