davsclaus opened a new pull request, #27499: URL: https://github.com/apache/camel/pull/27499
## Description https://issues.apache.org/jira/browse/CAMEL-25417 An opened project is listed as Stopped until it runs. When it runs, its app should stand in for it. The two were linked by directory only: the project folder had to be the directory the app reports. A folder of route files is run with `camel run --source-dir=<folder>` from the working directory of the monitor. Its app reports that directory, or, when a runtime is chosen, a copy in `.camel-jbang-run/<time>`. So the project stayed listed as Starting next to its running app: ``` 29858 custom-kamelet [dev] 4.23.0-SNAPSHOT 1/1 Running - custom-kamelet ⚙ Starting ``` Now the monitor keeps the process that F10 launched for the project. The app whose pid is that process, or a descendant of it, stands in for the project. The directory check stays for runs started outside the monitor. Maven projects, which run from their own folder, were linked before and still are. ## Tests `OpenedProjectLifecycleTest.aFolderRunWithF10IsFoundByItsProcess`: - an app in a `.camel-jbang-run` copy is linked through the launched process; - an app with the same name that was not launched for the project is not linked. The camel-jbang-plugin-tui module: 1757 tests pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
