Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(dependency): Issue of brave-bom version conflict resolution while enforcing dependencies from kork-bom in spinnaker services. #943

Merged
merged 1 commit into from
Mar 23, 2022

Conversation

j-sandy
Copy link
Contributor

@j-sandy j-sandy commented Mar 23, 2022

Refer issues :
spinnaker/spinnaker#6623
spinnaker/spinnaker#6624

The issue of brave-bom conflict was observed in all the spinnaker services while enforcing dependencies from kork-bom.
In all the spinnaker services, io.zipkin.brave dependency is introduced by the means of maven imported kork-bom. After introduction of enforcedPlatform, it adhere to the version of brave package provided by Hoxton.SR4, because io.zipkin.brave:brave-bom is not part of spinnaker-dependencies.gradle in kork and its just a constraint here.
To fix this issue, introduced brave-bom dependency with desired version and removed it from constraint section under spinnaker-dependencies.gradle

api(platform("io.zipkin.brave:brave-bom:${versions.brave}"))

The desired version of brave-bom (5.12.3) is supported by org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR5. It can be considered to exclude this dependency after upgrade of Hoxton.SR5.

… enforcing dependencies from kork-bom in spinnaker services.

Refer issues :
spinnaker/spinnaker#6623
spinnaker/spinnaker#6624

The issue of brave-bom conflict was observed in all the spinnaker services while enforcing dependencies from kork-bom.
In all the spinnaker services, io.zipkin.brave dependency is introduced by the means of maven imported kork-bom. After introduction of enforcedPlatform, it adhere to the version of brave package provided by Hoxton.SR4, because io.zipkin.brave:brave-bom is not part of spinnaker-dependencies.gradle in kork and its just a constraint here.
To fix this issue, introduced brave-bom dependency with desired version and removed it from constraint section under spinnaker-dependencies.gradle

api(platform("io.zipkin.brave:brave-bom:${versions.brave}"))

The desired version of brave-bom (5.12.3) is supported by org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR5. It can be considered to exclude this dependency after upgrade of Hoxton.SR5.
@dbyron-sf dbyron-sf added the ready to merge Approved and ready for merge label Mar 23, 2022
@mergify mergify bot added the auto merged label Mar 23, 2022
@mergify mergify bot merged commit bded5fa into spinnaker:master Mar 23, 2022
@j-sandy j-sandy deleted the zipkin-brave-fix branch March 24, 2022 04:00
ylebedeva pushed a commit to ylebedeva/kork that referenced this pull request May 3, 2022
… enforcing dependencies from kork-bom in spinnaker services. (spinnaker#943)

Refer issues :
spinnaker/spinnaker#6623
spinnaker/spinnaker#6624

The issue of brave-bom conflict was observed in all the spinnaker services while enforcing dependencies from kork-bom.
In all the spinnaker services, io.zipkin.brave dependency is introduced by the means of maven imported kork-bom. After introduction of enforcedPlatform, it adhere to the version of brave package provided by Hoxton.SR4, because io.zipkin.brave:brave-bom is not part of spinnaker-dependencies.gradle in kork and its just a constraint here.
To fix this issue, introduced brave-bom dependency with desired version and removed it from constraint section under spinnaker-dependencies.gradle

api(platform("io.zipkin.brave:brave-bom:${versions.brave}"))

The desired version of brave-bom (5.12.3) is supported by org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR5. It can be considered to exclude this dependency after upgrade of Hoxton.SR5.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants