Claus Ibsen created CAMEL-25417:
-----------------------------------
Summary: camel-jbang - An opened folder run with F10 stays listed
as Starting next to its running app
Key: CAMEL-25417
URL: https://issues.apache.org/jira/browse/CAMEL-25417
Project: Camel
Issue Type: Bug
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.23.0
A project opened in the camel-jbang monitor (a folder of route files) is listed
as Stopped until it runs; when it runs, its app should stand in for it. They
are linked by directory: the project folder must be the directory the app
reports.
A folder of route files is run with camel run --source-dir=<folder> from the
monitor's working directory, so the app reports that directory, or with a
runtime chosen (e.g. camel-main) a copy in <working
directory>/.camel-jbang-run/<time>. Neither is the project folder, so the
project stays listed as Starting (then Stopped) next to its running app:
{noformat}
29858 custom-kamelet [dev] 4.23.0-SNAPSHOT 1/1 Running
- custom-kamelet ⚙ Starting
{noformat}
Maven projects are run from their own folder and are linked.
Proposal: remember the process the monitor launched for the project, and link
the app whose pid is that process or one of its descendants; the directory
check stays for runs started outside the monitor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
