In Eclipse IDE, launch camel-debug-adapter launch configuration.
From command-line, launch mvn clean verify.
For Eclipse, see https://github.com/camel-tooling/camel-dap-client-eclipse#how-to-use-the-debug-adapter-for-apache-camel
For VS Code, replace the jar in jars folder and read how to configure a launch configuration.
You can use the Test camel-dap-server launch configuration in Debug mode.
To test with the Client integration of Eclipse IDE:
-
Install Eclipse LSP4E in your Eclipse Desktop instance
-
Build the Camel Debug Adapter Jar
-
Launch the Camel application that you want to debug
-
Create a
Debug Adapter Launcherconfiguration- Select
launch a Debug Server using the following arguments - In
commandfield, setjava - In
Argumentsfield, set-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=3000 -jar <pathTo>/camel-dap-server-xxx.jar - Select
Monitor Debug Adapter launch process - In
Launch Parameters (Json)field, set
{ "request": "attach" }- Click
Debug
- Select
-
Connect Remote Java Application to debug Camel DAP server project
- Create a
Remote Java Applicationconfiguration - In
projectfield, setcamel-dap-server - In
portfield, set3000 - Select
Allow termination of remote VM - Click
Debug
- Create a
-
You can now set breakpoints in textual Camel route definition and Camel Debug Adapter project
- Update pom to not use snapshot version
- Provide Pull Request (PR)
- Merge PR if OK
- Check that a GitHub Actions build is triggered and successful
- Create corresponding tag
- Check that the artifact is available on https://repo1.maven.org/maven2/com/github/camel-tooling/camel-dap-server/ . It usually takes up to 30 minutes.
- Update pom to use next snapshot version
- Provide PR
- Merge PR if OK