BUILD_AND_RUN_TIME_FIXED configuration is not actually fixed #19438
Assignees
Labels
Comments
stuartwdouglas
added a commit
to stuartwdouglas/quarkus
that referenced
this issue
Aug 17, 2021
This means that if you set a value using a system property when building the application it will now override the application.properties that is packaged in the application (but not an external application.properties on the file system). Otherwise the behaviour is very confusing, with build time config values only taking effect if they are not overriding a property in application.properties. Relates to (but does not fully fix) quarkusio#19438
stuartwdouglas
added a commit
to stuartwdouglas/quarkus
that referenced
this issue
Aug 17, 2021
This means that if you set a value using a system property when building the application it will now override the application.properties that is packaged in the application (but not an external application.properties on the file system). Otherwise the behaviour is very confusing, with build time config values only taking effect if they are not overriding a property in application.properties. Relates to (but does not fully fix) quarkusio#19438
stuartwdouglas
added a commit
to stuartwdouglas/quarkus
that referenced
this issue
Aug 17, 2021
This means that if you set a value using a system property when building the application it will now override the application.properties that is packaged in the application (but not an external application.properties on the file system). Otherwise the behaviour is very confusing, with build time config values only taking effect if they are not overriding a property in application.properties. Relates to (but does not fully fix) quarkusio#19438
stuartwdouglas
added a commit
to stuartwdouglas/quarkus
that referenced
this issue
Aug 17, 2021
This means that if you set a value using a system property when building the application it will now override the application.properties that is packaged in the application (but not an external application.properties on the file system). Otherwise the behaviour is very confusing, with build time config values only taking effect if they are not overriding a property in application.properties. Relates to (but does not fully fix) quarkusio#19438
|
Fixed in #20932 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
At runtime these classes are not initialized with the build time value. You get a warning but they are initialized from the runtime config.
'Specified build/runtime' values also currently have lower priority than the packaged application.properties, so building with system properties to override config only works if the confg is not present in application.properties.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: