Read build parameters also from application.properties #12498
Labels
Comments
Artur-
changed the title
|
The same rule should apply to the application.yml and yaml file for consistency. |
Artur-
added a commit
that referenced
this issue
Dec 7, 2021
…if present Reads "pnpm.enable", "require.home.node", "useDeprecatedV14Bootstrapping" and "eagerServerLoad" from application.properties. In the propertis file, all the keys must be prefixed with "vaadin." Fixes #12498
Artur-
added a commit
that referenced
this issue
Dec 7, 2021
…if present Reads "pnpm.enable", "require.home.node", "useDeprecatedV14Bootstrapping" and "eagerServerLoad" from application.properties. In the propertis file, all the keys must be prefixed with "vaadin." Fixes #12498
Artur-
added a commit
that referenced
this issue
Dec 7, 2021
…if present Reads "pnpm.enable", "require.home.node", "useDeprecatedV14Bootstrapping" and "eagerServerLoad" from application.properties. In the propertis file, all the keys must be prefixed with "vaadin." Fixes #12498
Artur-
added a commit
that referenced
this issue
Dec 22, 2021
…if present Reads "pnpm.enable", "require.home.node", "useDeprecatedV14Bootstrapping" and "eagerServerLoad" from application.properties. In the propertis file, all the keys must be prefixed with "vaadin." Fixes #12498
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug / feature
In a V22 Spring Boot project, you can define development mode to use npm instead of pnpm by adding
to
src/main/resources/application.propertiesYou can see on startup (
mvn) that this works:However, when you do a production build as
mvn package -Pproductionyou can see that pnpm is used:This is bad in many ways: unexpected, given lock file is not used, production doesn't match dev, ...
Expected behavior
The values you set in
src/main/resources/application.propertieswould be used also for the production build.The text was updated successfully, but these errors were encountered: