Skip to content

CAMEL-27005: camel-launcher - the generate plugin installs on first use instead of being bundled - #30163

Merged
davsclaus merged 2 commits into
mainfrom
CAMEL-27005-launcher-generate-on-first-use
Nov 16, 2026
Merged

davsclaus merged 2 commits into
mainfrom
CAMEL-27005-launcher-generate-on-first-use

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

CAMEL-27005

The Camel CLI launcher no longer bundles the generate plugin. The plugin and the OpenAPI generator it uses take up a fifth of the download. camel generate installs the plugin on first use from Maven Central, the same way camel edit does.

launcher distribution (local build) before after
jars in lib/ 342 284
bin.tar.gz 113.4 MB 90.8 MB

Changes

  • camel-launcher/pom.xml: removes the camel-jbang-plugin-generate dependency. The commonmark pin stays: tui needs a core at least as new as its commonmark-ext-* modules. The generate plugin, once installed, uses that core too, because its class loader is parent-first. The pom comment now explains this.
  • CamelLauncherMain: removes generate from the embedded plugins.
  • CamelLauncherTest: generate is not among the launcher commands, is still a plugin command (so it installs on first use), and neither GeneratePlugin nor openapi-generator is on the launcher classpath.
  • Docs: the plugin section in camel-jbang-projects.adoc says which plugins the launcher bundles. The 4.24 upgrade guide has an entry about the download on first use.

Who else uses generate

  • camel run --open-api uses a template, not the generate plugin.
  • The MCP camel_openapi_* tools run in the separate camel-jbang-mcp runner, which has its own dependencies.
  • Kaoto doesn't call camel generate: its OpenAPI import is written in TypeScript.

Tested

  • All 419 camel-launcher tests pass, 47 skipped.
  • I unpacked the distribution and ran it with a throwaway home:
    • The first camel generate rest --input petstore-v3.json printed Installed plugin: generate, wrote the REST DSL and exited with 0.
    • --dto wrote the 8 model classes through openapi-generator.
    • camel plugin get lists the plugin, and camel --help shows generate.

Claude Code on behalf of davsclaus

🤖 Generated with Claude Code

…se instead of being bundled

The generate plugin and the OpenAPI generator it uses are 58 jars and a
fifth of the Camel CLI download. camel generate installs the plugin on
first use, as for camel edit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@davsclaus davsclaus added this to the 4.24.0 milestone Nov 16, 2026
@davsclaus davsclaus added the dsl label Nov 16, 2026
@davsclaus davsclaus self-assigned this Nov 16, 2026
@github-actions github-actions Bot added the docs label Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs
  • dsl/camel-jbang/camel-launcher

🔬 Scalpel shadow comparison — Scalpel: 1 of 726 tested, 0 compile-only — current: 1 all tested

Maveniverse Scalpel detected 1 affected modules (current approach: 1).

Skip-tests mode would test 1 modules (2 direct + 0 downstream), skip tests for 0 (generated code, meta-modules)

Modules Scalpel would test (1)
  • camel-launcher-container ← depends on affected reactor module org.apache.camel:camel-launcher

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-launcher. The related integration tests in dsl/camel-jbang/camel-jbang-it are excluded from CI. Consider running them manually:

mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test
All tested modules (3 modules, 51.4s total)

Total reactor time: 51.4s

Module Duration Status
Camel :: Launcher 34.4s SUCCESS
Camel :: Docs 16.5s SUCCESS
Camel :: Launcher :: Container 0.6s SUCCESS

Top 20 slowest modules:

  • Camel :: Launcher (34.4s)
  • Camel :: Docs (16.5s)
  • Camel :: Launcher :: Container (0.6s)

⚙️ View full build and test results

@davsclaus davsclaus added the enhancement New feature or request label Nov 16, 2026
The embedded plugins are lambdas now (CAMEL-27045, #30199); the generate plugin stays out of the list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>

@gnodet-bot gnodet-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. No issues found.

This review was generated by an AI agent, Hermès on behalf of @gnodet.

@davsclaus
davsclaus merged commit b6100d4 into main Nov 16, 2026
14 checks passed
@davsclaus
davsclaus deleted the CAMEL-27005-launcher-generate-on-first-use branch November 16, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs dsl enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants