Aiven-Open / Aiven-Open/common-util

Simplify relationship with the parent pom

未關閉
#18 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Java
星號
0
分支
0
PR 合併指標
30 天內沒有已合併 PR

描述

# What is currently missing?

We currently define quite a few ``, and context in `` and `` in the parent pom, then proceed to override or ignore them in the child pom. This makes it difficult to review what is happening in version bumps.

For example, there's really no need to manage all the google dependencies via the bom in the parent pom if they are introduce in this module, or to define `commons.lang3.version>` in the parent pom if we're *not* going to put the dependency in the parent ``. This applies even more when we override it here in the child module.

Likewise with other context from the parent pom that is repeated throughout other modules like `` and ``.

# How could this be improved?

Define dependencies and versions where they are introduced into the module.

Trim repeated elements from child poms.

# Is this a feature you would work on yourself?

* [ ] I plan to open a pull request for this feature

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。