oscerd opened a new pull request, #28233:
URL: https://github.com/apache/camel/pull/28233

   ## Backport of #28175
   
   Port of #28175 (squash 2f05680c9562) onto `camel-4.18.x`.
   
   **Original PR:** #28175 - CAMEL-25462: camel-platform-http-main - management 
settings ignored on a shared server port
   **Original author:** @oscerd
   **Target branch:** `camel-4.18.x`
   
   Not a straight cherry-pick, so reviewers are requested:
   - `ManagementHttpServer`: the change applies as is; only an import line was 
merged by hand.
   - `KameletMain` and `KameletMainMcpManagementHostTest` are left out: `camel 
run --mcp` does not exist on this branch,
     so there is no loopback default to adjust.
   - `platform-http-main.adoc`: the new "Sharing the port with the management 
server" section is added; the "Downloading
     files" section next to it in the original diff is `main`-only content and 
is not brought over.
   - No catalog copies of the docs on this branch; the generated metadata was 
regenerated on the branch.
   - The upgrade-guide note for 4.18.6 already lives on `main`.
   
   Build: full reactor `mvn clean install -DskipTests -DskipITs` on the branch: 
BUILD SUCCESS (657/657 modules); it regenerated the `camel.management.port` 
description in the camel-main metadata (and its catalog copy) and in 
`main.adoc`, committed here; `camel-platform-http-main`
   tests: 25/25 (`ManagementHttpServerSharedPortTest` 9/9). Without the call to 
the new check in `ManagementHttpServer`, the five `sharedPortRejects*` tests 
fail with "Expected ... to be thrown, but nothing was thrown".
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-25462
   
   _Claude Code on behalf of Andrea Cosentino (@oscerd)_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to