[camel-quarkus] branch main updated: documentation fixes

[pp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ppalaga pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/main by this push:
     new 6923d06  documentation fixes
6923d06 is described below

commit 6923d06e00a8eb41fefd22b3ad82df15f153e19f
Author: aldettinger <al...@gmail.com>
AuthorDate: Wed Apr 14 15:57:40 2021 +0200

    documentation fixes
---
 .../contributor-guide/create-new-extension.adoc    |  7 ------
 .../contributor-guide/promote-jvm-to-native.adoc   |  7 ------
 .../ROOT/pages/user-guide/configuration.adoc       | 29 ----------------------
 .../modules/ROOT/pages/user-guide/first-steps.adoc |  2 +-
 4 files changed, 1 insertion(+), 44 deletions(-)

diff --git a/docs/modules/ROOT/pages/contributor-guide/create-new-extension.adoc b/docs/modules/ROOT/pages/contributor-guide/create-new-extension.adoc
index 079c7d0..e85b180 100644
--- a/docs/modules/ROOT/pages/contributor-guide/create-new-extension.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/create-new-extension.adoc
@@ -66,13 +66,6 @@ Check the xref:contributor-guide/extension-metadata.adoc[Extension metadata] pag
 9. Complete the integration test module under `integration-tests/foo-abc`. Make sure you test both the consumer and the
    producer of the component (if the component supports both). Make sure the tests are passing both in the JVM mode
    (`mvn test`) and in the native mode (`mvn verify -Pnative`).
-+
-[TIP]
-====
-If your test application is going to be configured via `camel.component.*` properties, you need to add the
-`camel-quarkus-main` dependency to the test project. See the xref:user-guide/configuration.adoc[Bootstrap] section of
-the User guide for more details.
-====
 
 10. In case of problems, consult the https://quarkus.io/guides/extension-authors-guide[Quarkus extension author's guide],
    ask for help in the given GitHub issue or via https://camel.zulipchat.com[Camel Quarkus chat].
diff --git a/docs/modules/ROOT/pages/contributor-guide/promote-jvm-to-native.adoc b/docs/modules/ROOT/pages/contributor-guide/promote-jvm-to-native.adoc
index a986317..763dc5c 100644
--- a/docs/modules/ROOT/pages/contributor-guide/promote-jvm-to-native.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/promote-jvm-to-native.adoc
@@ -46,13 +46,6 @@ $ cd integration-tests/foo
 $ mvn clean verify -Pnative
 ----
 +
-[TIP]
-====
-If your test application is going to be configured via `camel.component.*` properties, you need to add the
-`camel-quarkus-main` dependency to the test project. See the xref:user-guide/configuration.adoc[Bootstrap] section of
-the User guide for more details.
-====
-+
 Consider shifting some tasks from runtime to build time.
 The https://quarkus.io/guides/extension-authors-guide[Quarkus extension author's guide] may be a good ally for this.
 
diff --git a/docs/modules/ROOT/pages/user-guide/configuration.adoc b/docs/modules/ROOT/pages/user-guide/configuration.adoc
index cb51535..e947f2d 100644
--- a/docs/modules/ROOT/pages/user-guide/configuration.adoc
+++ b/docs/modules/ROOT/pages/user-guide/configuration.adoc
@@ -103,35 +103,6 @@ Since 1.8.0, all its functionality moved to `camel-quarkus-core`.
 In addition to support configuring Camel through properties, `camel-quarkus-core` allows you to use conventions to configure the Camel behavior.
 For example, if there is a single `ExchangeFormatter` instance in the CDI container, then it will automatically wire that bean to the `LogComponent`.
 
-
-`camel-quarkus-core` also brings the option to write https://quarkus.io/guides/command-mode-reference[Quarkus Command Mode Applications] with control about when the Camel runtime should start:
-
-[source,java]
-----
-import io.quarkus.runtime.Quarkus;
-import io.quarkus.runtime.annotations.QuarkusMain;
-import org.apache.camel.quarkus.main.CamelMainApplication;
-
-@QuarkusMain
-public class Main {
-    public static void main(String... args) {
-        //
-        // your logic here
-        //
-
-        Quarkus.run(CamelMainApplication.class, args); // <1>
-    }
-}
-----
-<1> Start Quarkus and the Camel Quarkus runtime
-
-[NOTE]
-====
-It is recommended to perform very little logic in the Java Main.
-====
-
-Find more details about Camel Quarkus command line applications in this link:/blog/2020/07/command-line-utility-with-camel-quarkus/[blog post].
-
 == What's next?
 
 We recommend to continue with xref:user-guide/cdi.adoc[CDI].
diff --git a/docs/modules/ROOT/pages/user-guide/first-steps.adoc b/docs/modules/ROOT/pages/user-guide/first-steps.adoc
index a56945a..3b61dbc 100644
--- a/docs/modules/ROOT/pages/user-guide/first-steps.adoc
+++ b/docs/modules/ROOT/pages/user-guide/first-steps.adoc
@@ -58,7 +58,7 @@ Check the documentation of the given plugin to discover how to create projects i
 
 === Camel content assist
 
-The follwing plugins provide support for content assist when editing Camel routes and `application.properties`:
+The following plugins provide support for content assist when editing Camel routes and `application.properties`:
 
 * https://marketplace.visualstudio.com/items?itemName=redhat.vscode-apache-camel[VS Code Language support for Camel] - a part of the https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack[Camel extension pack]
 * https://marketplace.eclipse.org/content/language-support-apache-camel[Eclipse Desktop Language Support for Camel] - a part of https://tools.jboss.org/[Jboss Tools] and https://developers.redhat.com/products/codeready-studio[CodeReady Studio]