jamesnetherton commented on PR #29693:
URL: https://github.com/apache/camel/pull/29693#issuecomment-6826601479
Thanks Federico, all addressed (1 and 2 folded into the CAMEL-23172 commit):
1. **Leading-zero numbers:** `YamlTrees.newMapper()` now disables
`PARSE_OCTAL_NUMBERS`, and `YamlTestSupport` does the same. `08540`, `0830` and
`09` read as numbers again, so validation and the consumer check work. `~`,
`Null`, `0x1F` and `+12` read as before; `0123` now reads as 123 (YAML 1.2
decimal). Your route is a test in `YamlValidatorScalarLeniencyTest` and in
`EndpointConsumersTest`, and `YamlTreesTest` checks `08540`.
2. **Upgrade guide:**
- `streaming: yes`: the guide now says the route fails to start. The test
comment is corrected too.
- Map body: the json-validator section says it still reads only JSON
text, bytes and streams, so a `Map` or `List` body fails, as before. This is
called out against *Jackson 2 nodes*.
- Nesting: the json-validator section notes the Jackson 3 limits (more
than 500 levels now fails) and points to *Limits* in the Jackson 3 section, as
the other component sections do.
3. **json-schema-validator version:** `camel-mcp-server`, `camel-openai` and
`camel-mcp-server-api` (test scope) now declare `json-schema-validator` with
`${networknt-json-schema-validator-version}` (folded into the CAMEL-26469
commit), so they resolve 3.0.9 like camel-json-validator. It is pinned in the
modules rather than managed in `camel-parent`. Maven 3 does not apply a
dependency's parent `dependencyManagement` to its transitive dependencies: an
app whose only dependency is `camel-mcp-server` still got 3.0.6 with a managed
entry, and gets 3.0.9 with the module pin. A parent entry would also force
3.0.9 onto the WireMock tests of other modules (camel-pubnub,
camel-rest-openapi, camel-jbang-run...), where WireMock brings 1.5.9.
_Claude Code on behalf of jamesnetherton_
--
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]
