Re: [PR] chore: camel-jbang - one SLF4J provider in camel-jbang-mcp, and camel_get_log names no picocli frame as the user's code [camel]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #28118:
URL: https://github.com/apache/camel/pull/28118#issuecomment-6272955042

   <!-- ci-tested-modules -->
   :test_tube: **CI tested the following changed modules:**
   
   - `dsl/camel-jbang/camel-jbang-core`
   - `dsl/camel-jbang/camel-jbang-mcp`
   
   ---
   
   <details><summary>:microscope: Scalpel shadow comparison — Scalpel: 5 of 707 tested, 0 compile-only — current: 5 all tested</summary>
   
   [Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **5 affected modules** (current approach: 5).
   
   **Skip-tests mode would test 5 modules** (2 direct + 0 downstream), **skip tests for 0** (generated code, meta-modules)
   
   <details><summary>Modules Scalpel would test (5)</summary>
   
   - `camel-jbang-mcp` ← own pom dsl/camel-jbang/camel-jbang-mcp/pom.xml changed
   - `camel-jbang-plugin-mcp` ← depends on affected reactor module org.apache.camel:camel-jbang-core
   - `camel-jbang-plugin-tui` ← depends on affected reactor module org.apache.camel:camel-jbang-core
   - `camel-jbang-plugin-validate` ← depends on affected reactor module org.apache.camel:camel-jbang-core
   - `camel-launcher-container` ← depends on affected reactor module org.apache.camel:camel-launcher
   
   </details>
   
   > :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel)
   
   </details>
   
   :warning: **Some tests are disabled on GitHub Actions** (`@DisabledIfSystemProperty(named = "ci.env.name")`) and require manual verification:
   
   - `dsl/camel-jbang/camel-jbang-core`: 2 test(s) disabled on GitHub Actions
   - `dsl/camel-jbang/camel-jbang-mcp`: 2 test(s) disabled on GitHub Actions
   
   :bulb: **Manual integration tests recommended:**
   
   > You modified `dsl/camel-jbang/camel-jbang-core`. 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
   > ```
   
   <details><summary>All tested modules (14 modules, 2m 56s total)</summary>
   
   **Total reactor time:** 2m 56s
   
   | Module | Duration | Status |
   | --- | --- | --- |
   | Camel :: Launcher | 54.0s | SUCCESS |
   | Camel :: JBang :: MCP | 45.2s | SUCCESS |
   | Camel :: JBang :: Plugin :: Validate | 32.6s | SUCCESS |
   | Camel :: JBang :: Plugin :: Testing | 15.5s | SUCCESS |
   | Camel :: JBang :: Plugin :: Kubernetes | 15.0s | SUCCESS |
   | Camel :: Coverage | 5.3s | SUCCESS |
   | Camel :: JBang :: Plugin :: Edit | 1.8s | SUCCESS |
   | Camel :: JBang :: Plugin :: MCP | 1.6s | SUCCESS |
   | Camel :: JBang :: Plugin :: Generate | 1.5s | SUCCESS |
   | Camel :: JBang :: Integration tests | 1.2s | SUCCESS |
   | Camel :: JBang :: Main | 1.0s | SUCCESS |
   | Camel :: Launcher :: Container | 0.8s | SUCCESS |
   | Camel :: JBang :: Core | n/a |  |
   | Camel :: JBang :: Plugin :: TUI | n/a |  |
   
   **Top 20 slowest modules:**
   - `Camel :: Launcher` (54.0s)
   - `Camel :: JBang :: MCP` (45.2s)
   - `Camel :: JBang :: Plugin :: Validate` (32.6s)
   - `Camel :: JBang :: Plugin :: Testing` (15.5s)
   - `Camel :: JBang :: Plugin :: Kubernetes` (15.0s)
   - `Camel :: Coverage` (5.3s)
   - `Camel :: JBang :: Plugin :: Edit` (1.8s)
   - `Camel :: JBang :: Plugin :: MCP` (1.6s)
   - `Camel :: JBang :: Plugin :: Generate` (1.5s)
   - `Camel :: JBang :: Integration tests` (1.2s)
   - `Camel :: JBang :: Main` (1.0s)
   - `Camel :: Launcher :: Container` (0.8s)
   
   </details>
   
   ---
   :gear: [View full build and test results](https://github.com/apache/camel/actions/runs/39272859513)


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org