You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2020/11/03 22:28:21 UTC
[camel-quarkus] branch master updated: fix(docs): use cross
reference URLs (2)
This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/master by this push:
new 771142d fix(docs): use cross reference URLs (2)
771142d is described below
commit 771142de2f9d99723a72199c10bde34327a699b4
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Tue Nov 3 23:28:04 2020 +0100
fix(docs): use cross reference URLs (2)
Additional manual changes reverted in 72edb0b9ca836ca48d757bcc6bee5024d6c035f1
---
docs/modules/ROOT/pages/contributor-guide/extension-metadata.adoc | 2 +-
docs/modules/ROOT/pages/contributor-guide/release-guide.adoc | 4 ++--
docs/modules/ROOT/pages/index.adoc | 4 ++--
.../ROOT/pages/reference/extensions/microprofile-metrics.adoc | 4 ++--
docs/modules/ROOT/pages/user-guide/bootstrap.adoc | 6 +++---
docs/modules/ROOT/pages/user-guide/native-mode.adoc | 2 +-
docs/modules/ROOT/pages/user-guide/observability.adoc | 2 +-
extensions/microprofile-metrics/runtime/src/main/doc/usage.adoc | 6 +++---
8 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/extension-metadata.adoc b/docs/modules/ROOT/pages/contributor-guide/extension-metadata.adoc
index f31d2a1..2ac9060 100644
--- a/docs/modules/ROOT/pages/contributor-guide/extension-metadata.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/extension-metadata.adoc
@@ -30,7 +30,7 @@ The data comes from the following
sources:
* `name`: comes from `pom.xml`'s `<name>`
-* `description`: taken from https://camel.apache.org/manual/latest/camel-catalog.html[Camel Catalog]. If the given
+* `description`: taken from xref:latest@manual::camel-catalog.adoc[Camel Catalog]. If the given
extension contains more than one component, language or data format, their descriptions are concatenated and a warning
is issued in the log. The value from Camel Catalog can be overridden by setting a `<description>` in the
`pom.xml` of the given extension's runtime module.
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index 8eb8905..4679e3c 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -3,10 +3,10 @@
:page-aliases: release-guide.adoc
The process is _mutatis mutandis_ the same as for the main Apache Camel repository - see the
-https://camel.apache.org/manual/latest/release-guide.html[Release guide] page of the Camel documentation.
+xref:latest@manual::release-guide.adoc[Release guide] page of the Camel documentation.
Here, just a sketch of the repeating part, after you have performed the initial setup following the
-https://camel.apache.org/manual/latest/release-guide.html[Camel Release guide].
+xref:latest@manual::release-guide.adoc[Camel Release guide].
== Pre release tasks
diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
index abc039a..c3c77bf 100644
--- a/docs/modules/ROOT/pages/index.adoc
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -1,7 +1,7 @@
= Apache Camel extensions for Quarkus
-This project aims to bring the awesome integration capabilities of https://camel.apache.org/manual/latest/[Apache Camel]
-and its vast https://camel.apache.org/components/latest/[component library] to the
+This project aims to bring the awesome integration capabilities of xref:latest@manual::index.adoc[Apache Camel]
+and its vast xref:latest@components::index.adoc[component library] to the
https://quarkus.io/[Quarkus runtime].
This enables users to take advantage of the performance benefits, https://quarkus.io/vision/developer-joy[developer joy]
diff --git a/docs/modules/ROOT/pages/reference/extensions/microprofile-metrics.adoc b/docs/modules/ROOT/pages/reference/extensions/microprofile-metrics.adoc
index 4b62e22..09dd1c5 100644
--- a/docs/modules/ROOT/pages/reference/extensions/microprofile-metrics.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/microprofile-metrics.adoc
@@ -35,7 +35,7 @@ Check the xref:user-guide/index.adoc[User guide] for more information about writ
== Usage
-The https://camel.apache.org/components/latest/microprofile-metrics-component.html[microprofile-metrics] component automatically exposes a set of Camel application metrics. Some of these include:
+The xref:latest@components::microprofile-metrics-component.adoc[microprofile-metrics] component automatically exposes a set of Camel application metrics. Some of these include:
=== Camel Context metrics
@@ -150,7 +150,7 @@ The total number of all failures handled for the route
All metrics are tagged with the name of the Camel Context and the id of the route where applicable.
-You can also produce your own customized metrics in your Camel routes. For more information, refer to the https://camel.apache.org/components/latest/microprofile-metrics-component.html[microprofile-metrics] component documentation.
+You can also produce your own customized metrics in your Camel routes. For more information, refer to the xref:latest@components::microprofile-metrics-component.adoc[microprofile-metrics] component documentation.
Metrics are exposed to Quarkus as application metrics and they can be browsed at http://localhost:8080/metrics/application.
diff --git a/docs/modules/ROOT/pages/user-guide/bootstrap.adoc b/docs/modules/ROOT/pages/user-guide/bootstrap.adoc
index b61d35b..3bbb019 100644
--- a/docs/modules/ROOT/pages/user-guide/bootstrap.adoc
+++ b/docs/modules/ROOT/pages/user-guide/bootstrap.adoc
@@ -63,7 +63,7 @@ public static class EventHandler {
== Camel Main
To configure components and other aspects of Apache Camel through properties, you can add the `camel-quarkus-main`
-extension which brings functionalities from https://camel.apache.org/components/latest/others/main.html[Apache Camel
+extension which brings functionalities from xref:latest@components:others:main.adoc[Apache Camel
Main] to Camel Quarkus.
In the example below, we apply the same configuration as the one from the Java example above by using properties:
@@ -142,7 +142,7 @@ Spring XML with `<beans>` or Blueprint XML with `<blueprint>` elements are not s
==== REST DSL
-The Camel https://camel.apache.org/manual/latest/rest-dsl.html[REST DSL] can be defined in XML and configured with Camel Main via a property:
+The Camel xref:latest@manual::rest-dsl.adoc[REST DSL] can be defined in XML and configured with Camel Main via a property:
[source,properties]
----
@@ -166,7 +166,7 @@ The XML for the REST configuration looks like:
==== Route Templates
-https://camel.apache.org/manual/latest/route-template.html[Route templates] can be defined in XML and configured with Camel Main via a property:
+xref:latest@manual::route-template.adoc[Route templates] can be defined in XML and configured with Camel Main via a property:
[source,properties]
----
diff --git a/docs/modules/ROOT/pages/user-guide/native-mode.adoc b/docs/modules/ROOT/pages/user-guide/native-mode.adoc
index 8b7bf5d..c19cdc2 100644
--- a/docs/modules/ROOT/pages/user-guide/native-mode.adoc
+++ b/docs/modules/ROOT/pages/user-guide/native-mode.adoc
@@ -44,7 +44,7 @@ At the end of the day, resources matching `include-patterns` are marked for incl
[[using-onexception-clause-in-native-mode]]
== Using onException clause in native mode
-When using https://camel.apache.org/manual/latest/exception-clause.html[camel onException handling] in native mode, it is the application developer's responsibility to register exception classes for reflection.
+When using xref:latest@manual::exception-clause.adoc[camel onException handling] in native mode, it is the application developer's responsibility to register exception classes for reflection.
For instance, having a camel context with onException handling as below:
diff --git a/docs/modules/ROOT/pages/user-guide/observability.adoc b/docs/modules/ROOT/pages/user-guide/observability.adoc
index 4925c85..884f6ea 100644
--- a/docs/modules/ROOT/pages/user-guide/observability.adoc
+++ b/docs/modules/ROOT/pages/user-guide/observability.adoc
@@ -4,7 +4,7 @@
Health & liveness checks are supported via the
xref:reference/extensions/microprofile-health.adoc[MicroProfile Health] extension. They can be configured via the
-https://camel.apache.org/manual/latest/health-check.html[Camel Health] API or via
+xref:latest@manual::health-check.adoc[Camel Health] API or via
https://quarkus.io/guides/microprofile-health[Quarkus MicroProfile Health].
All configured checks are available on the standard MicroProfile Health endpoint URLs:
diff --git a/extensions/microprofile-metrics/runtime/src/main/doc/usage.adoc b/extensions/microprofile-metrics/runtime/src/main/doc/usage.adoc
index b3f834f..51c5f3c 100644
--- a/extensions/microprofile-metrics/runtime/src/main/doc/usage.adoc
+++ b/extensions/microprofile-metrics/runtime/src/main/doc/usage.adoc
@@ -1,4 +1,4 @@
-The https://camel.apache.org/components/latest/microprofile-metrics-component.html[microprofile-metrics] component automatically exposes a set of Camel application metrics. Some of these include:
+The xref:latest@components::microprofile-metrics-component.adoc[microprofile-metrics] component automatically exposes a set of Camel application metrics. Some of these include:
=== Camel Context metrics
@@ -113,6 +113,6 @@ The total number of all failures handled for the route
All metrics are tagged with the name of the Camel Context and the id of the route where applicable.
-You can also produce your own customized metrics in your Camel routes. For more information, refer to the https://camel.apache.org/components/latest/microprofile-metrics-component.html[microprofile-metrics] component documentation.
+You can also produce your own customized metrics in your Camel routes. For more information, refer to the xref:latest@components::microprofile-metrics-component.adoc[microprofile-metrics] component documentation.
-Metrics are exposed to Quarkus as application metrics and they can be browsed at http://localhost:8080/metrics/application.
\ No newline at end of file
+Metrics are exposed to Quarkus as application metrics and they can be browsed at http://localhost:8080/metrics/application.