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

acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 0feb1b7  Provide blogpost article for VS Code Java debug using 
right-click menu
0feb1b7 is described below

commit 0feb1b7f12b9880aeff563fe6a2d5c07953ff628
Author: AurĂ©lien Pupier <[email protected]>
AuthorDate: Mon May 17 14:23:04 2021 +0200

    Provide blogpost article for VS Code Java debug using right-click menu
    
    Signed-off-by: AurĂ©lien Pupier <[email protected]>
---
 .../2021/01/DebugInVSCodeWithCamelK1.3.0/index.md  |   2 ++
 .../1-CreateJavaCamelKIntegration.gif              | Bin 0 -> 214734 bytes
 .../2-putBreakpoint.gif                            | Bin 0 -> 886244 bytes
 .../3-startIntegration.gif                         | Bin 0 -> 226718 bytes
 .../4-CamelK-JavaDebug-fromRightClick.gif          | Bin 0 -> 197591 bytes
 .../JavaDebuggingInVSCode-iteration2}/index.md     |  35 ++++++---------------
 6 files changed, 11 insertions(+), 26 deletions(-)

diff --git a/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md 
b/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md
index 0d1b1e6..5a9c7c2 100644
--- a/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md
+++ b/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md
@@ -6,6 +6,8 @@ categories: ["Tooling","Camel K"]
 preview: "How to Java debug a Camel K integration in VS Code with Camel K 
1.3.0"
 ---
 
+UPDATED ON 17 May 2021: More recent related content available in [this 
blogpost](/blog/2021/05/JavaDebuggingInVSCode-iteration2).
+
 Camel K 1.3.0 is providing a new feature to Java debug deployed integrations. 
Even if Camel K 1.3.0 is [not fully 
compatible](https://github.com/apache/camel-k/issues/1872) with VS Code Tooling 
for Apache Camel K extension, it remains possible to leverage the VS Code Java 
debugging capabilities.
 
 I recorded a [video](https://youtu.be/cFPuxd1Je3c) which is following the 
steps in this blogpost. I let you choose your preferred way to discover how to 
java debug your Camel K integration in VS Code.
diff --git 
a/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/1-CreateJavaCamelKIntegration.gif
 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/1-CreateJavaCamelKIntegration.gif
new file mode 100644
index 0000000..1cc9b6a
Binary files /dev/null and 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/1-CreateJavaCamelKIntegration.gif
 differ
diff --git 
a/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/2-putBreakpoint.gif 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/2-putBreakpoint.gif
new file mode 100644
index 0000000..aa0016e
Binary files /dev/null and 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/2-putBreakpoint.gif 
differ
diff --git 
a/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/3-startIntegration.gif 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/3-startIntegration.gif
new file mode 100644
index 0000000..81322ec
Binary files /dev/null and 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/3-startIntegration.gif 
differ
diff --git 
a/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/4-CamelK-JavaDebug-fromRightClick.gif
 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/4-CamelK-JavaDebug-fromRightClick.gif
new file mode 100644
index 0000000..dcdec88
Binary files /dev/null and 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/4-CamelK-JavaDebug-fromRightClick.gif
 differ
diff --git a/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md 
b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/index.md
similarity index 63%
copy from content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md
copy to content/blog/2021/05/JavaDebuggingInVSCode-iteration2/index.md
index 0d1b1e6..2f5038e 100644
--- a/content/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/index.md
+++ b/content/blog/2021/05/JavaDebuggingInVSCode-iteration2/index.md
@@ -1,20 +1,18 @@
 ---
-title: "How to Java debug a Camel K integration in VS Code with Camel K 1.3.0"
-date: 2021-01-20
+title: "How to Java debug a Camel K integration in VS Code - second iteration"
+date: 2021-05-17
 authors: [apupier]
 categories: ["Tooling","Camel K"]
-preview: "How to Java debug a Camel K integration in VS Code with Camel K 
1.3.0"
+preview: "How to Java debug a Camel K integration in VS Code - second 
iteration"
 ---
 
-Camel K 1.3.0 is providing a new feature to Java debug deployed integrations. 
Even if Camel K 1.3.0 is [not fully 
compatible](https://github.com/apache/camel-k/issues/1872) with VS Code Tooling 
for Apache Camel K extension, it remains possible to leverage the VS Code Java 
debugging capabilities.
+Camel K is providing a new feature to Java debug deployed integrations. Before 
VS Code Tooling for Apache Camel K 0.0.25, more complex steps were required to 
leverage the VS Code Java debugging capabilities as explained in [this previous 
blogpost](/blog/2021/01/DebugInVSCodeWithCamelK1.3.0/).
 
-I recorded a [video](https://youtu.be/cFPuxd1Je3c) which is following the 
steps in this blogpost. I let you choose your preferred way to discover how to 
java debug your Camel K integration in VS Code.
+I recorded a [video](https://youtu.be/pFj21YvzZm0) which is following the 
steps in this blogpost.
 
 # Requirements
 
-- [VS Code Extension Pack for Apache 
Camel](https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack)
-- Uncheck _Camelk -> Integrations: Auto-upgrade_ in _File -> Preferences -> 
Settings -> Extensions -> Apache Camel K Tooling_
-- [Camel K 1.3.0 binary](/download/#camel-k) available on command-line
+- [VS Code Extension Pack for Apache 
Camel](https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack)
 with VS Code Tooling for Apache Camel K 0.0.25+
 - Camel K deployed to a cluster. In this demo, we will use a Camel K instance 
deployed on minikube.
 
 # How to java debug
@@ -60,26 +58,11 @@ You can then start the integration:
 
 Note: If starting in --dev, it will allow to automatically reload the 
Integration. But take care, debugger will need to be restarted on each change. 
Meaning that the next two steps will need to be repeated.
 
-#### Start debugger on runtime
+#### Debug
 
-- Open terminal: _terminal -> New Terminal_
-- Call _kamel debug demo_ (replace _demo_ by the integration name that appears 
in _Apache Camel K Integrations_ view if you choose a different name.
+In Integrations view, wait that the integration is running, then right-click 
on the integration and select _Start Java debugger on Camel K Integration_.
 
-![Start debugger on runtime](4-startDebuggerOnRuntime.gif)
-
-Note: Take care to use the kamel 1.3.0 binaries.
-
-#### Attach debugger
-
-- In the left panel, select the _Run & Debug_ container
-- Click on _create a launch.json_
-- Remove the default _configuration_
-- Use completion to pick the _Java: Attach_
-- Provide a meaningful name
-- Update port, by default Camel K is using _5005_
-- Click on the green triangle to _Start debugging_
-
-![Attach debugger](5-AttachDebugger.gif)
+![Debug Integration](./4-CamelK-JavaDebug-fromRightClick.gif)
 
 #### Enjoy
 

Reply via email to