Fork for pb-universe: networknt 3.x / Jackson 3 + io.github.productboardlabs release - #1
Merged
Conversation
networknt 3.x replaced its Jackson 2 node API with Jackson 3 and removed the
getSchema/validate(JsonNode) overloads this library called, so consumers that
put networknt 3.x on the classpath hit NoSuchMethodError when the first schema
is compiled. Feed networknt JSON text via its InputFormat.JSON entry points,
move the custom Format validators to Jackson 3 nodes, and pin the Jackson 3 BOM
to the version networknt depends on. The public API is unchanged.
One behaviour change: a value beyond Double.MAX_VALUE is now rejected as a type
error ("number expected") rather than reaching the custom double-format
validator. The value is still rejected.
Refs atlassian#21
….1-pb.1) Retarget coordinates com.atlassian.oai -> io.github.productboardlabs across all reactor modules and set version 3.0.1-pb.1, point SCM/url at the fork, and add the Sonatype central-publishing-maven-plugin (publishingServerId=central, autoPublish=true) mirroring productboardlabs/jackson-kafka-avro-serializer so `mvn clean deploy` publishes to Maven Central. Builds on top of the networknt 3.x migration (PR atlassian#24) so swagger/OpenAPI request validation is compatible with Jackson 3 / networknt 3.x. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Productboard fork of
openapi-request-validatorso pb-universe can run OpenAPI request validation on networknt json-schema-validator 3.x / Jackson 3, alongside the MCP / Spring AI 2.0 stack (which forces networknt 3.x). Upstream is effectively unmaintained (atlassian/openapi-request-validator#24 — the fix — is a stalled external draft with no maintainer left to merge).Commits
getSchema(com.fasterxml…JsonNode)overloads this library called. Feeds schema + instance to networknt as JSON text viaInputFormat.JSON; customFormatvalidators move to Jackson 3 nodes.com.atlassian.oai.validator.*public API unchanged. networknt2.0.1→3.0.4.com.atlassian.oai→io.github.productboardlabs, version3.0.1-pb.1, SCM/url → this fork, and addcentral-publishing-maven-plugin(publishingServerId=central,autoPublish=true).Verified
openapi-request-validator-corebuilds green — 90 tests, 0 failures on networknt 3.0.4 (incl. the networknt-3.x probe tests).openapi-request-validator-spring-webmvcpackages cleanly under the new coordinates.Release (manual, per DEPLOYMENT.md)
mvn clean deploy→ publishesio.github.productboardlabs:openapi-request-validator-spring-webmvc:3.0.1-pb.1to Maven Central (needs GPG key + Sonatype "Stargate" token). pb-universe then swapscom.atlassian.oai:swagger-request-validator-spring-webmvc:3.0.0→ the fork coordinate (note artifact renameswagger-→openapi-; Java packagecom.atlassian.oai.validator.*is unchanged).