[
https://issues.apache.org/jira/browse/CAMEL-24728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-24728:
--------------------------------
Fix Version/s: 4.25.0
> camel-jbang: stage 3 - migrate Camel TUI to camel-jbang-runner Java API
> -----------------------------------------------------------------------
>
> Key: CAMEL-24728
> URL: https://issues.apache.org/jira/browse/CAMEL-24728
> Project: Camel
> Issue Type: Sub-task
> Reporter: Ricardo Martinez
> Priority: Trivial
> Fix For: 4.25.0
>
>
> h2. Motivation
> The Camel TUI currently builds a {{camel run --runtime=<x> ...}} argv and
> spawns a subprocess via ProcessBuilder. This ties the TUI and other projects
> like Kaoto, to the CLI option surface and breaks whenever CLI options change.
> With camel-jbang-runner available, the TUI can call the Java API directly.
> h2. What changes
> Changes in {{camel-jbang-plugin-tui}} only. No changes to camel-jbang-core,
> camel-jbang-export or camel-jbang-runner (except additive changes to
> LaunchOptions if a needed field is missing).
> * RunOptionsForm / LaunchManager build an {{ExportRequest}} +
> {{LaunchOptions}} instead of assembling a {{camel run}} argv, then start the
> {{LaunchCommand}} returned by {{ProjectRunner}}.
> * {{--runtime=jbang}} keeps spawning the CLI binary — that runtime is by
> definition in-process and the TUI must not host user routes in its own JVM.
> * Log tailing (~/.camel/<name>.log) is unchanged; {{LaunchOptions.logFile}}
> carries the path.
> h2. Compatibility
> No change to CLI options or behaviour. No change to other modules.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
