This is an automated email from the ASF dual-hosted git repository. jamesnetherton pushed a commit to branch 2.7.x in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
commit 748bbe59e0fa3b94fa4e5c48a71045fd5a8fcd7d Author: aldettinger <[email protected]> AuthorDate: Fri Feb 11 17:24:58 2022 +0100 Remove freemarker inaccurate documentation --- .../pages/reference/extensions/freemarker.adoc | 42 ---------------------- .../runtime/src/main/doc/configuration.adoc | 42 ---------------------- 2 files changed, 84 deletions(-) diff --git a/docs/modules/ROOT/pages/reference/extensions/freemarker.adoc b/docs/modules/ROOT/pages/reference/extensions/freemarker.adoc index 89a3c1b..3255a54 100644 --- a/docs/modules/ROOT/pages/reference/extensions/freemarker.adoc +++ b/docs/modules/ROOT/pages/reference/extensions/freemarker.adoc @@ -45,48 +45,6 @@ The `allowContextMapAll` option is not supported in native mode as it requires r == Additional Camel Quarkus configuration -== Class path resources - -For the FreeMarker templates loaded from class path to work flawlessly in native mode, you need to list all your -template files using `quarkus.native.resources.includes` and `quarkus.native.resources.excludes` -options in `application.properties`. - -Here is an example: If your application's resources look like this - -[source,shell] ----- -$ tree src/main/resources -src/main/resources -└── templates - ├── email.ftl - ├── page.html - └── unwanted-file.txt ----- - -and if your configuration is like this - -[source,properties] ----- -quarkus.native.resources.includes = templates/*.ftl,templates/*.html -quarkus.native.resources.excludes = templates/unwanted* ----- - -then, resources `templates/email.ftl` and `templates/page.ftl` will be available in the native image, -while file `unwanted-file.txt` will not be available. - -You can thus use the available templates in a Camel route, e.g.: - -[source,java] ----- -public class MyRoutes extends RouteBuilder { - @Override - public void configure() { - from("direct:example") - .to("freemarker:templates/email.ftl") - } -} ----- - == Quarkiverse Freemarker and its configuration Camel Quarkus Freemarker uses dev/index.html[Quarkiverse Freemarker] under the hood. diff --git a/extensions/freemarker/runtime/src/main/doc/configuration.adoc b/extensions/freemarker/runtime/src/main/doc/configuration.adoc index 323fd41..0bc095f 100644 --- a/extensions/freemarker/runtime/src/main/doc/configuration.adoc +++ b/extensions/freemarker/runtime/src/main/doc/configuration.adoc @@ -1,45 +1,3 @@ -== Class path resources - -For the FreeMarker templates loaded from class path to work flawlessly in native mode, you need to list all your -template files using `quarkus.native.resources.includes` and `quarkus.native.resources.excludes` -options in `application.properties`. - -Here is an example: If your application's resources look like this - -[source,shell] ----- -$ tree src/main/resources -src/main/resources -└── templates - ├── email.ftl - ├── page.html - └── unwanted-file.txt ----- - -and if your configuration is like this - -[source,properties] ----- -quarkus.native.resources.includes = templates/*.ftl,templates/*.html -quarkus.native.resources.excludes = templates/unwanted* ----- - -then, resources `templates/email.ftl` and `templates/page.ftl` will be available in the native image, -while file `unwanted-file.txt` will not be available. - -You can thus use the available templates in a Camel route, e.g.: - -[source,java] ----- -public class MyRoutes extends RouteBuilder { - @Override - public void configure() { - from("direct:example") - .to("freemarker:templates/email.ftl") - } -} ----- - == Quarkiverse Freemarker and its configuration Camel Quarkus Freemarker uses dev/index.html[Quarkiverse Freemarker] under the hood.
