This is an automated email from the ASF dual-hosted git repository. nfilotto pushed a commit to branch some-improvements-build-time-properties.adoc in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit ecb85e31d4adf64bf9e063b9935ec1d3471d7512 Author: Nicolas Filotto <[email protected]> AuthorDate: Wed Aug 3 12:31:54 2022 +0200 Some various improvements * Remove the dev mode flag from the command as it is not required and brings some noice * Fix the file name in the command * Reformulate for clarity --- docs/modules/ROOT/pages/configuration/build-time-properties.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/modules/ROOT/pages/configuration/build-time-properties.adoc b/docs/modules/ROOT/pages/configuration/build-time-properties.adoc index b1ab7b130..713c3f182 100644 --- a/docs/modules/ROOT/pages/configuration/build-time-properties.adoc +++ b/docs/modules/ROOT/pages/configuration/build-time-properties.adoc @@ -18,7 +18,7 @@ from('timer:build-property') In order to give a value to the `quarkus.application.name` property you can pass it using the command line with the `--build-property` flag: ---- -kamel run --build-property=quarkus.application.name=my-super-application build-property-route.groovy --dev +kamel run --build-property=quarkus.application.name=my-super-application build-property-route.groovy ---- You can provide more than one single `build-property` at once by just adding the flag repeatedly (ie, `--build-property=prop1=val1 --build-property=prop2=val2 ...`) @@ -26,7 +26,7 @@ You can provide more than one single `build-property` at once by just adding the [[build-time-props-file]] == Property File -Repeating the property flag when you have many *build time configuration* may be cumbersome. Usually you deal with property files instead. You will be able to use the _file_ syntax available for `--build-property` flag. Here, as an example you have a property files with 2 `Quarkus` properties: +Repeating the `--build-property` flag when you have many *build time configuration* may be cumbersome. Usually you deal with property files instead. You will be able to use the _file_ syntax available for `--build-property` flag. Here, as an example you have a property file with 2 `Quarkus` properties: [source,properties] .quarkus.properties @@ -45,7 +45,7 @@ from('timer:build-property') The `quarkus.banner.enabled` is configured to show the banner during the `Integration` startup. Let's use `--build-property` flag in conjunction with file: ---- -kamel run --build-property=file:quarkus.properties build-property-file-route.groovy --dev +kamel run --build-property=file:quarkus.properties build-property-route.groovy ---- The property file is parsed and its properties configured on the `Integration`. As soon as the application starts, you will see the log with the expected configuration. @@ -58,4 +58,4 @@ If you have a property repeated more than once, the general rule is that the las [[build-time-runtime-conf]] == Run time properties -If you're looking for *runtime properties configuration* you can look at the xref:configuration/runtime-properties.adoc[runtime properties] section. \ No newline at end of file +If you're looking for *runtime properties configuration* you can look at the xref:configuration/runtime-properties.adoc[runtime properties] section.
