[camel-k] branch master updated: Point to documentation for debugging using VS Code

[as...@apache.org]

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

astefanutti pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/master by this push:
     new bc0dabe  Point to documentation for debugging using VS Code
bc0dabe is described below

commit bc0dabee039caf90ba7761c1b8d03296c727d736
Author: Aurélien Pupier <ap...@redhat.com>
AuthorDate: Fri Feb 12 20:25:41 2021 +0100

    Point to documentation for debugging using VS Code
---
 docs/modules/ROOT/pages/troubleshooting/debugging.adoc | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/modules/ROOT/pages/troubleshooting/debugging.adoc b/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
index be4bfeb..3e229da 100644
--- a/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
+++ b/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
@@ -1,9 +1,13 @@
 = Debugging Camel K Integrations
 
 Sometimes integrations can fail or behave unexpectedly for unknown reasons and a developer needs to investigate the cause of such behavior.
-Attaching a debugger to an integration is a common way to start the investigation.
+Attaching a Java debugger to an integration is a common way to start the investigation.
 
-Even if Camel K integrations run on a Kubernetes cluster, it's very easy to attach a debugger to the remote integration using the CLI.
+Even if Camel K integrations run on a Kubernetes cluster, it's very easy to attach a Java debugger to the remote integration using the CLI.
+
+If you're a VS Code user, you can watch this link:https://www.youtube.com/watch?v=cFPuxd1Je3c[video] or follow this link:https://camel.apache.org/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/[blogpost].
+
+Find below a more generic explanation using IntelliJ.
 
 Suppose you just launched an integration using the following command: