Publish Maven Bill Of Materials (BOM) pom

After reading up on it I see that it can be helpful if a project has both direct and transitive driver dependencies. And it's a simple change so OK for me.

I agree that a BOM would make more sense with driver 4.0 and its transitive dependencies. Let’s tentatively schedule this for 4.5.0.

Given the 4.x driver, there are a few dependencies (shaded guava, protocol implementation) that do not share the same version number. While it's totally doable to use version placeholders, importing a BOM and referring to just the artifacts is the preferred consumption of multi-module dependencies so that users can consume these dependencies in a simplified approach.

Maven does not benefit that much from an omitted `version` tag. Looking at Gradle, the dependency declaration is much more streamlined and there you see an immediate benefit. So +1 for a BOM for the 4.x driver.

Hi,
Would that provide much value though? I see the advantage for spring-data, where the components listed in the BOM have different versions. But in our case all driver modules share the same version, so you could easily extract it in a variable:

Is there anything that a BOM handles better?