Full Stack App with Spring dev mode packaged war doesn't work in tomcat

When using platform snapshot and flow-maven-plugin snapshot the war resulting from running mvn package (without production mode) fails to deploy in tomcat. More info in https://github.com/vaadin/bakery-app-starter-flow-spring/issues/824

[Legioth]

That would mean that any build that explicitly or implicitly uses mvn package would be in an intermediate development mode that does non-production logging and such, but still doesn’t use the webpack dev server. I believe that would be a significant improvement over the current situation.

The one situation that would be slightly weird is still if you build a .war or otherwise deploy directly from e.g. Eclipse, since it would then pick a mode based on the last time you did run something through Maven. I think this would still be a relatively good trade-off.

[caalador]

We could have the build-frontend goal add a conf "dev-server": false, into flow-build-info.json so that then if you do a package the dev-server wouldn’t be used, but we would fall on the generated bundles. This would mean also that the prepare-frontend goal should always remove this configuration so that when running mvn jetty:run we wouldn’t be left without the dev-server even if we didn’t clean.