Skip to content

Commit 02ecd05

Browse files
Fix vale errors
1 parent 270f877 commit 02ecd05

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/flow/production/troubleshooting.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,8 +102,8 @@ The application won't start after adding the `flow-server-production-mode` depen
102102
One potential cause of this problem is that the `build-frontend` of the `flow-maven-plugin` wasn't executed, either because the plugin is missing from the [filename]`pom.xml` file, or it's missing in the configuration. To resolve this, add the `flow-maven-plugin` to your Maven `build` block. Make sure it's visible in your production mode profile. Then enable the `build-frontend` goal.
103103

104104

105-
Front-end resources are missing or not loaded in the running application.::
106-
A production build can result in a running application without properly loaded front-end resources due to a misconfigured `vaadin-maven-plugin`.
105+
Frontend resources are missing or not loaded in the running application.::
106+
A production build can result in a running application without properly loaded frontend resources due to a misconfigured `vaadin-maven-plugin`.
107107
+
108108
To ensure that the production build packages all resources correctly, make sure the `vaadin-maven-plugin` is executed after the `maven-compiler-plugin`. This can be achieved either configuring the execution goal of `vaadin-maven-plugin` to run after the goal targeted by `maven-compiler-plugin`, or if both target the same goal, placing the `vaadin-maven-plugin` definition after the `maven-compiler-plugin` in your `pom.xml`.
109109

0 commit comments

Comments
 (0)