This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch camel-2.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-2.x by this push:
new 79945b4 change xref links for splitting faq in camel-2.x
79945b4 is described below
commit 79945b4b6ba66aa63403c904314fee4fae7a224d
Author: aashnajena <[email protected]>
AuthorDate: Fri Apr 3 16:43:40 2020 +0530
change xref links for splitting faq in camel-2.x
---
camel-core/src/main/docs/modules/ROOT/pages/properties-component.adoc | 2 +-
camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc | 2 +-
camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc | 2 +-
components/camel-beanstalk/src/main/docs/beanstalk-component.adoc | 2 +-
components/camel-jetty9/src/main/docs/jetty-component.adoc | 2 +-
components/camel-spring/src/main/docs/spring.adoc | 2 +-
components/camel-undertow/src/main/docs/undertow-component.adoc | 2 +-
components/camel-zipkin/src/main/docs/zipkin.adoc | 4 ++--
docs/components/modules/ROOT/pages/beanstalk-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jetty-component.adoc | 2 +-
docs/components/modules/ROOT/pages/spring.adoc | 2 +-
docs/components/modules/ROOT/pages/undertow-component.adoc | 2 +-
docs/components/modules/ROOT/pages/zipkin.adoc | 4 ++--
13 files changed, 15 insertions(+), 15 deletions(-)
diff --git
a/camel-core/src/main/docs/modules/ROOT/pages/properties-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/properties-component.adoc
index 119a3b4..4b22df2 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/properties-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/properties-component.adoc
@@ -96,7 +96,7 @@ This works much like you would do if using Spring's
`<property-placeholder>` tag. However Spring have a limitation which
prevents 3rd party frameworks to leverage Spring property placeholders
to the fullest. See more at
-xref:latest@manual::faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How
do
+xref:latest@manual:faq:how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How
do
I use Spring Property Placeholder with Camel XML].
[TIP]
diff --git a/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
index 3c79ded..d43f1e7 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
@@ -29,7 +29,7 @@ advanced scheduling.
TIP:*Specify time in human friendly format*
In *Camel 2.3* onwards you can specify the time in
-xref:latest@manual::faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[human
+xref:latest@manual:faq:how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[human
friendly syntax].
diff --git a/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
index 6e2f21b..2bec6f6 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
@@ -278,7 +278,7 @@ With Spring XML:
== Dynamic stylesheets
To provide a dynamic stylesheet at runtime you can define a dynamic URI.
-See xref:latest@manual::faq/how-to-use-a-dynamic-uri-in-to.adoc[How to use a
dynamic URI in
+See xref:latest@manual:faq:how-to-use-a-dynamic-uri-in-to.adoc[How to use a
dynamic URI in
to()] for more information.
*Available as of Camel 2.9 (removed in 2.11.4, 2.12.3 and 2.13.0)*
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 53db7be..48e7a37 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -47,7 +47,7 @@ beanstalk://localhost:11300/tube1+tube2
Tube name will be URL decoded, so if your tube names include special
characters like + or ?, you need to URL-encode them appropriately, or
-use the RAW syntax, see
xref:latest@manual::faq/how-do-i-configure-endpoints.adoc[more
+use the RAW syntax, see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[more
details here].
By the way, you cannot specify several tubes when you are writing jobs
diff --git a/components/camel-jetty9/src/main/docs/jetty-component.adoc
b/components/camel-jetty9/src/main/docs/jetty-component.adoc
index 5a7ca3b..c73a019 100644
--- a/components/camel-jetty9/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty9/src/main/docs/jetty-component.adoc
@@ -315,7 +315,7 @@ If you need to expose a Jetty endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual::faq/how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
+xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
wildcards].
If you actually want to expose routes by HTTP and already have a
diff --git a/components/camel-spring/src/main/docs/spring.adoc
b/components/camel-spring/src/main/docs/spring.adoc
index 9f5c0c0..9e74f25 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -337,7 +337,7 @@ SpringCamelContext lazily fetching components from the
spring context
for the scheme name you use for Endpoint
URIs.
-For more detail see
xref:latest@manual::faq/how-do-i-configure-endpoints.adoc[Configuring
+For more detail see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[Configuring
Endpoints and Components].
== CamelContextAware
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc
b/components/camel-undertow/src/main/docs/undertow-component.adoc
index bb89212..20b02f2 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -220,7 +220,7 @@ If you need to expose an Undertow endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual::faq/how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
+xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
diff --git a/components/camel-zipkin/src/main/docs/zipkin.adoc
b/components/camel-zipkin/src/main/docs/zipkin.adoc
index 9fffa3d..bdd553e 100644
--- a/components/camel-zipkin/src/main/docs/zipkin.adoc
+++ b/components/camel-zipkin/src/main/docs/zipkin.adoc
@@ -75,14 +75,14 @@ uses the rules from Intercept.
|includeMessageBody |false |Whether to include the Camel message body in the
zipkin traces.
This is not recommended for production usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|includeMessageBodyStreams |false |Whether to include message bodies that are
stream based in the zipkin
traces. This requires enabling streamcaching on the
routes or globally on the CamelContext. This is not recommended for production
usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|===
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index 542856d..5e88d2a 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -48,7 +48,7 @@ beanstalk://localhost:11300/tube1+tube2
Tube name will be URL decoded, so if your tube names include special
characters like + or ?, you need to URL-encode them appropriately, or
-use the RAW syntax, see
xref:latest@manual::faq/how-do-i-configure-endpoints.adoc[more
+use the RAW syntax, see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[more
details here].
By the way, you cannot specify several tubes when you are writing jobs
diff --git a/docs/components/modules/ROOT/pages/jetty-component.adoc
b/docs/components/modules/ROOT/pages/jetty-component.adoc
index cb6820f..c2d1c2a 100644
--- a/docs/components/modules/ROOT/pages/jetty-component.adoc
+++ b/docs/components/modules/ROOT/pages/jetty-component.adoc
@@ -316,7 +316,7 @@ If you need to expose a Jetty endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual::faq/how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
+xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
wildcards].
If you actually want to expose routes by HTTP and already have a
diff --git a/docs/components/modules/ROOT/pages/spring.adoc
b/docs/components/modules/ROOT/pages/spring.adoc
index 2204c76..819cbb4 100644
--- a/docs/components/modules/ROOT/pages/spring.adoc
+++ b/docs/components/modules/ROOT/pages/spring.adoc
@@ -338,7 +338,7 @@ SpringCamelContext lazily fetching components from the
spring context
for the scheme name you use for Endpoint
URIs.
-For more detail see
xref:latest@manual::faq/how-do-i-configure-endpoints.adoc[Configuring
+For more detail see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[Configuring
Endpoints and Components].
== CamelContextAware
diff --git a/docs/components/modules/ROOT/pages/undertow-component.adoc
b/docs/components/modules/ROOT/pages/undertow-component.adoc
index 4841a26..36694cb 100644
--- a/docs/components/modules/ROOT/pages/undertow-component.adoc
+++ b/docs/components/modules/ROOT/pages/undertow-component.adoc
@@ -221,7 +221,7 @@ If you need to expose an Undertow endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual::faq/how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
+xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
diff --git a/docs/components/modules/ROOT/pages/zipkin.adoc
b/docs/components/modules/ROOT/pages/zipkin.adoc
index 573bd26..d3e8607 100644
--- a/docs/components/modules/ROOT/pages/zipkin.adoc
+++ b/docs/components/modules/ROOT/pages/zipkin.adoc
@@ -76,14 +76,14 @@ uses the rules from Intercept.
|includeMessageBody |false |Whether to include the Camel message body in the
zipkin traces.
This is not recommended for production usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|includeMessageBodyStreams |false |Whether to include message bodies that are
stream based in the zipkin
traces. This requires enabling streamcaching on the
routes or globally on the CamelContext. This is not recommended for production
usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|===
