In progress Jackson release process can break builds depending on latest version

I’m not familiar with the release process of Jackson but I assume it can take a while. During this process builds depending on Jackson can break due to already published modules depending on unpublished ones.

E.g.: let’s say we have a project that depends on jackson-module-abc which depends on jackson-module-xyz. If the release process publishes jackson-module-abc first our build will fail till jackson-module-xyz is published. If the publishing order is the opposite, there would be no problems.

To give a more realistic example: if the bom is published first, whoever consumes the bom can be broken until the other modules are published:

> Could not find com.fasterxml.jackson.module:jackson-module-scala_2.13:2.13.0.
  Searched in the following locations:
    - https://repo.maven.apache.org/maven2/com/fasterxml/jackson/module/jackson-module-scala_2.13/2.13.0/jackson-module-scala_2.13-2.13.0.pom
    - file:/Users/jivanov/.m2/repository/com/fasterxml/jackson/module/jackson-module-scala_2.13/2.13.0/jackson-module-scala_2.13-2.13.0.pom
  Required by:
      project :micrometer-samples-core > project :micrometer-registry-stackdriver > com.fasterxml.jackson.core:jackson-databind:2.13.0 > com.fasterxml.jackson:jackson-bom:2.13.0

(full error message: https://ge.micrometer.io/s/vywlbquulkvdc/failure#1) I don’t think this is a huge issue but we bump into this at ~every jackson release with micrometer.

(I wanted to open this under https://github.com/FasterXML/jackson but the description asked me not to so I opened it here because this is the module I encountered this issue with, please move it if it is not appropriate.)

[pjfanning]

https://github.com/FasterXML/jackson-module-scala/issues/547#issuecomment-931955303

[pjfanning]

I don’t understand your build process but the jackson release takes a while as there are many modules. Why do you need to use jackson 2.13.0 within hours of its release?