Remove various version overrides from module poms.#18708
Conversation
github-actions
Bot
added
Area - Batch Ingestion
Area - Querying
Area - Metrics/Event Emitting
Area - Streaming Ingestion
Area - Lookups
Area - Dependencies
Kubernetes
Area - Ingestion
Area - MSQ
Many poms explicitly specified versions for dependencies and plugins that have centrally-managed versions in the master pom's dependencyManagement and pluginManagement section. For the most part, the overrides were simply restating the centrally-managed version, so they weren't causing an actual divergence. The most substantive change is that hamcrest is upgraded from 1.3 to 2.2. Version 2.2 was already being used by kubernetes-overlord-extensions.
|
I wonder if there's a way to do this with Druid versions too? Instead of stating |
yeah, that would be nice too. |
I'm not sure if there's a way to do that while still preserving maven's ability to do
I actually wanted to do this but wasn't sure how, so I skipped it. Do you happen to know how to implement a check like this for |
4 participants
Many poms explicitly specified versions for dependencies and plugins that have centrally-managed versions in the master pom's dependencyManagement and pluginManagement section.
For the most part, the overrides were simply restating the centrally-managed version, so they weren't causing an actual divergence. In these cases, removing the overrides simply improves maintainability by promoting the usages of dependencyManagement and pluginManagement.
The most substantive change is that hamcrest is upgraded from 1.3 to 2.2. Version 2.2 was already being used by kubernetes-overlord-extensions.