Highlight that vaadin-maven-plugin must always be defined after maven-compiler-plugin #4432
Description
There are several forum posts and GH tickets mentioning that sometimes when running an application in production mode results in error messages about missing resources (javascript, css, etc.).
An example: https://vaadin.com/forum/t/urgent-production-build-failed/178117
One of the causes is that the build-frontend goal gets executed before the Java classes are compiled by the maven compiler plugin (holds also for the kotlin compiler plugin), so the bytecode scanner cannot find any class to analyze.
The documentation should explicitly state that vaadin-maven-plugin must always be defined after maven-compiler-plugin.
Potential pages to update could be production build and troubleshooting.
If you think this issue is important, add a 👍 reaction to help the community and maintainers prioritize this issue.