Jackson Snapshot builds temporarily broken (likely due to Sonatype auth upgrade)

5 views
Skip to first unread message

Tatu Saloranta

unread,
Jun 15, 2024, 12:52:09 PMJun 15
to jacks...@googlegroups.com
Quick note: our automated CI releases -SNAPSHOT versions from pushes
to all 2.x branches and master (3.0.0). But it looks like something
broke yesterday -- I suspect it is due to Sonatype's deprecation of
the old token system, and I need to see what/how to upgrade.

In the meantime, SNAPSHOT versions available may be slightly outdated
until I fix the issue.

-+ Tatu +-

ps. In better news, we now have dual-dependent build system: pushes to
2.18 AND master of jackson-core and jackson-databind now trigger
cascading rebuilds (see
https://medium.com/@cowtowncoder/cascading-dependency-rebuilds-for-jackson-ci-5113d0b71631)
-- originally only 2.18 (default branch) was supported, but I added
secondary workflow for master so we ensure 3.0.0 branch also builds.
(obviously these are also affected by publishing problem, but once
that is resolved we should have much better visibility into breaking
changes across components)

Tatu Saloranta

unread,
Jun 16, 2024, 12:13:15 AMJun 16
to jacks...@googlegroups.com
Quick update: I was able to restore the ability to publish 2.18
components, including snapshots, by creating a user token for Sonatype
OSSRH repository and using that for authentication.

But interestingly enough this did NOT resolve the issue with 3.0
(master). I will need to work with Sonatype support to get that done
too, but right now 2.18 is still more important to have working so
that's good.

-+ Tatu +-

Tatu Saloranta

unread,
Jun 17, 2024, 8:25:33 PMJun 17
to jacks...@googlegroups.com
And after some more back and forth, Jackson 3.0 ("master" branch)
dependency builds work again, with Snapshot version publishing.
So both 2.18.0-SNAPSHOT and 3.0.0-SNAPSHOT dependencies should be
properly recreated

-+ Tatu +-
Reply all
Reply to author
Forward
0 new messages