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-website.git
The following commit(s) were added to refs/heads/main by this push:
new 530ef248 chore: add test plugin execution section to 4.21 blog
530ef248 is described below
commit 530ef248b4f76656dcdaad1ea420ac05f02c5456
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Jul 2 12:00:16 2026 +0200
chore: add test plugin execution section to 4.21 blog
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
content/blog/2026/07/camel421-whatsnew/index.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/blog/2026/07/camel421-whatsnew/index.md
b/content/blog/2026/07/camel421-whatsnew/index.md
index e5b76171..736fc878 100644
--- a/content/blog/2026/07/camel421-whatsnew/index.md
+++ b/content/blog/2026/07/camel421-whatsnew/index.md
@@ -139,6 +139,10 @@ Plugins are now loaded lazily. Built-in commands that do
not consume plugins
(such as `camel get`, `camel version`, `camel ps`) skip plugin discovery
entirely,
making these commands faster. Plugin classpath resolution is also cached.
+### Test plugin execution
+
+The test plugin used to call a separate JBang process for executing the test
commands. This has changed in the sense of directly calling the Citrus test
engine in the same Camel CLI JVM. This saves the additional indirection of
calling a separate JBang process and makes sure to always call the matching
Citrus version when using the test plugin in Camel. Also, users of Camel
launcher CLI will not require the JBang installation anymore just for running
the test plugin.
+
### Wrapper Renamed
The `camel wrapper` command now installs scripts as `camel` instead of
`camelw`.
