Skip to content

Flatten feign-bom so imports do not override consumer dependency management - #3508

Open
kalayciburak wants to merge 1 commit into
OpenFeign:masterfrom
kalayciburak:fix/feign-bom-flatten-import
Open

Flatten feign-bom so imports do not override consumer dependency management#3508
kalayciburak wants to merge 1 commit into
OpenFeign:masterfrom
kalayciburak:fix/feign-bom-flatten-import

Conversation

@kalayciburak

Copy link
Copy Markdown

Summary

Importing feign-bom into a consumer that already manages versions (for example Spring Boot) previously pulled feign-parent dependency management through the published BOM parent. That overrode consumer-managed artifacts such as Jackson.

This applies flatten-maven-plugin in bom mode on the committed feign-bom module and the sundr BOM template so the installed/deployed POM only manages Feign modules.

Fixes #3505

Verification

  • ./mvnw -N -Pquickbuild install
  • ./mvnw -pl feign-bom -Pquickbuild install
  • Installed feign-bom POM has no <parent> and no third-party dependencyManagement entries
  • Consumer with spring-boot-starter-parent 3.5.4:
    • Boot only: jackson-core 2.19.2
      • central feign-bom 13.13: jackson-core 2.22.0 (override bug)
      • local flattened feign-bom 13.14-SNAPSHOT: jackson-core 2.19.2 (Boot version kept)

…gement

Installing and deploying feign-bom previously published a POM that still
parented feign-parent. Importing that BOM into a project such as Spring Boot
also imported parent dependencyManagement (for example jackson-bom) and
overrode the consumer's managed versions.

Apply flatten-maven-plugin in bom mode on the BOM module and template so the
published artifact only manages Feign modules.

Fixes OpenFeign#3505
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BOM is not usable with spring-boot-starter-parent

1 participant