haisi / jackson-jspecify / 30202902458

100%

push

github

fix: correct jackson version pinning and add flatten-maven-plugin

Two bugs the first two failed v0.1.0 release attempts surfaced, neither
visible in local -Dquick/qa builds since dependency:tree was never part of
those checks:

1. Importing tools.jackson:jackson-bom (even declared before
   spring-boot-dependencies) did not reliably win the merged
   dependencyManagement - spring-boot-dependencies bundles its own older
   Jackson 3 line, and `mvn dependency:tree` showed 3.1.4/2.21 actually
   being used instead of the intended 3.2.1/2.22 combination, contrary to
   what "first import wins" would suggest. Fixed by pinning
   jackson-databind/jackson-core/jackson-annotations as direct
   dependencyManagement entries instead of an imported BOM - a direct entry
   always wins over one pulled in through any import, regardless of order.

2. Added org.codehaus.mojo:flatten-maven-plugin (release profile, ossrh
   mode): Maven Central's Publisher Portal validates each deployed module's
   raw pom.xml, not Maven's resolved in-memory model, so a child module's
   pom.xml (which only has a <parent> reference) was rejected for missing
   license/SCM/developer info and dependency versions - all of which are
   real, just only present in the parent POM's file on disk. Flattening
   inlines everything into a self-contained .flattened-pom.xml that gets
   installed/deployed instead.

Also added explicit <scm> to both child modules (matching the earlier <url>
fix): Maven's default inheritance appends the module's artifactId to the
parent's scm URLs when a child doesn't define its own, which flatten then
faithfully inlined as .git/jackson-jspecify - not a real URL.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

70 of 70 branches covered (100.0%)

Branch coverage included in aggregate %.

145 of 145 relevant lines covered (100.0%)

4.66 hits per line