This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new dff69dc Update debugger.adoc
dff69dc is described below
commit dff69dcd0cba5bf28c0a9552605928910c79b5ad
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed May 19 09:34:16 2021 +0200
Update debugger.adoc
---
docs/user-manual/modules/ROOT/pages/debugger.adoc | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/debugger.adoc
b/docs/user-manual/modules/ROOT/pages/debugger.adoc
index ce6a068..7e771b8 100644
--- a/docs/user-manual/modules/ROOT/pages/debugger.adoc
+++ b/docs/user-manual/modules/ROOT/pages/debugger.adoc
@@ -1,8 +1,6 @@
[[Debugger-Debugger]]
= Debugger
-*Since Camel 2.6*
-
Camel Debugger is much related to
Tracer, in fact they are sisters. Debugger is a
enhanced tracer with a debugger framework so that tooling can be
@@ -96,7 +94,7 @@ routing. The `ProcessorDefinition` and the `id` and
`shortName`
parameters is all information which tells you where in the route the
breakpoint was hit.
-TIP:There is also a `debugAfter` method which is invoked after the processor
+TIP: There is also a `debugAfter` method which is invoked after the processor
has been invoked. This allows you to _see_ what happens to the
Exchange right after it has invoked a processor in
the route.
