atiaomar1978-hub commented on PR #25202:
URL: https://github.com/apache/camel/pull/25202#issuecomment-5133118394

   _AI-generated comment on behalf of 
[atiaomar1978-hub](https://github.com/atiaomar1978-hub)_
   
   Pushed `3855e776` addressing @gnodet's review on [PR 
#25202](https://github.com/apache/camel/pull/25202):
   
   1. **Duplicate Run configuration** — `--openapi-ui` runtime keys now use 
`addOverrideProperty` only (same pattern as `--observe`); 
`camel.jbang.openapiUi` remains persisted via `writeSetting` like `--console`.
   2. **Swagger UI version coupling** — version is read from 
`META-INF/maven/org.webjars/swagger-ui/pom.properties` at runtime; Maven uses 
`${swagger-ui-version}` in `camel-platform-http-main/pom.xml`.
   3. **KameletMain REST overrides** — `camel.rest.component` / 
`camel.rest.apiContextPath` defaults apply only when not already configured in 
initial or override properties.
   4. **HTML defense-in-depth** — 
`OpenApiUiSupport.escapeForJavaScriptString()` before embedding `specPath` in 
the Swagger UI bootstrap script.
   5. **JBang metadata security** — `PrepareCamelJBangMojo` now emits 
`@Metadata(security=…)`; regenerated `camel.jbang.openapiUi` metadata with 
`"security": "insecure:dev"`.
   6. **Upgrade guide** — added `--openapi-ui` entry to the 4.22 upgrade guide.
   
   **New/extended tests:** explicit `--management-port` preservation, JS 
escaping + webjar version resolution, plus existing OpenApiUi HTTP/REST tests.
   
   ```bash
   mvn test -pl components/camel-platform-http-main 
-Dtest=OpenApiUiHttpServerTest,OpenApiUiRestMainTest,OpenApiUiSupportTest
   mvn test -pl dsl/camel-jbang/camel-jbang-core -Dtest=RunOpenApiUiOptionsTest
   ```
   
   All green locally (8 + 3 tests).


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