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.git
commit 7a599f6832c092ebecac77f9fc828704b93783b8
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Thu Jul 11 12:06:31 2019 +0530
more fixes for anchor not found errors
---
components/camel-cdi/src/main/docs/cdi.adoc | 1 +
.../src/main/docs/micrometer-component.adoc | 6 +++---
.../modules/ROOT/pages/micrometer-component.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/index.adoc | 14 +++++++-------
.../modules/ROOT/pages/scala-dsl-supported-languages.adoc | 2 +-
5 files changed, 15 insertions(+), 14 deletions(-)
diff --git a/components/camel-cdi/src/main/docs/cdi.adoc
b/components/camel-cdi/src/main/docs/cdi.adoc
index fcf0b33..d5e1fa3 100644
--- a/components/camel-cdi/src/main/docs/cdi.adoc
+++ b/components/camel-cdi/src/main/docs/cdi.adoc
@@ -47,6 +47,7 @@ type `DefaultCamelContext`.
Note that this bean can be customized programmatically and other Camel
context beans can be deployed in the application as well.
+[[CDI-Auto-detectingCamelroutes]]
=== Auto-detecting Camel routes
Camel CDI automatically collects all the `RoutesBuilder` beans in the
diff --git
a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index 45f60db..164f4df 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -14,7 +14,7 @@ endif::[]
The Micrometer component allows to collect various metrics directly
from Camel routes. Supported metric types
-are xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-distributionSummary[summary],
+are xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-summary[summary],
and xref:#MicrometerComponent-timer[timer]. http://micrometer.io/[Micrometer]
provides
simple way to measure the behaviour of an application. Configurable
reporting backends (via Micrometer registries) enable different integration
options for
@@ -307,7 +307,7 @@ from("direct:in")
----
-### [[MicrometerComponent-summary]]Distribution Summary
+=== [[MicrometerComponent-summary]]Distribution Summary
[source]
----
@@ -375,7 +375,7 @@ from("direct:in")
----
-### [[MicrometerComponent-timer]]Timer
+=== [[MicrometerComponent-timer]]Timer
[source]
----
diff --git a/docs/components/modules/ROOT/pages/micrometer-component.adoc
b/docs/components/modules/ROOT/pages/micrometer-component.adoc
index 45f60db..164f4df 100644
--- a/docs/components/modules/ROOT/pages/micrometer-component.adoc
+++ b/docs/components/modules/ROOT/pages/micrometer-component.adoc
@@ -14,7 +14,7 @@ endif::[]
The Micrometer component allows to collect various metrics directly
from Camel routes. Supported metric types
-are xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-distributionSummary[summary],
+are xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-summary[summary],
and xref:#MicrometerComponent-timer[timer]. http://micrometer.io/[Micrometer]
provides
simple way to measure the behaviour of an application. Configurable
reporting backends (via Micrometer registries) enable different integration
options for
@@ -307,7 +307,7 @@ from("direct:in")
----
-### [[MicrometerComponent-summary]]Distribution Summary
+=== [[MicrometerComponent-summary]]Distribution Summary
[source]
----
@@ -375,7 +375,7 @@ from("direct:in")
----
-### [[MicrometerComponent-timer]]Timer
+=== [[MicrometerComponent-timer]]Timer
[source]
----
diff --git a/docs/user-manual/modules/ROOT/pages/index.adoc
b/docs/user-manual/modules/ROOT/pages/index.adoc
index a3f5927..38b27df 100644
--- a/docs/user-manual/modules/ROOT/pages/index.adoc
+++ b/docs/user-manual/modules/ROOT/pages/index.adoc
@@ -1,9 +1,9 @@
= Summary
-* xref:#overview.adoc[Overview]
-* xref:#documentation.adoc[Documentation]
-* xref:#community.adoc[Community]
-* xref:#developers.adoc[Developers]
+* <<Overview>>
+* <<Documentation>>
+* <<Community>>
+* <<Developers>>
== Overview
@@ -16,7 +16,7 @@
== Documentation
-* xref:#user-guide.adoc[User Guide]
+* <<User Guide>>
* Manual
* xref:books.adoc[Books]
* Tutorials
@@ -25,8 +25,8 @@
* xref:architecture.adoc[Architecture]
* xref:enterprise-integration-patterns.adoc[Enterprise Integration Patterns]
* xref:dsl.adoc[DSL]
-* xref:#components.adoc[Components]
-* xref:#data-formats.adoc[Data Formats]
+* <<Components>>
+* <<Data Formats>>
* xref:languages.adoc[Languages]
=== User Guide
diff --git
a/docs/user-manual/modules/ROOT/pages/scala-dsl-supported-languages.adoc
b/docs/user-manual/modules/ROOT/pages/scala-dsl-supported-languages.adoc
index 4bdd2f6..2c7772a 100644
--- a/docs/user-manual/modules/ROOT/pages/scala-dsl-supported-languages.adoc
+++ b/docs/user-manual/modules/ROOT/pages/scala-dsl-supported-languages.adoc
@@ -11,7 +11,7 @@ You can use any of the supported Camel Languages in
the Scala DSL; see below for a couple of examples:
[[ScalaDSL-Supportedlanguages-Using]]
-Using xref:components::xpath-language.adoc[XPath]
+Using xref:xpath-language.adoc[XPath]
----------------------------
With the XPath trait, you have an additional method available on an
