Skip to content

Commit

Permalink
Manage fabric8 client version in framework
Browse files Browse the repository at this point in the history
* Due to quarkusio/quarkus#42656, this
  implements a workaround where we manage fabric8 version ourselves
  rather than letting Quarkus manage it, as this leads to binary
  incompatible versions of library.
  • Loading branch information
mjurc committed Aug 20, 2024
1 parent 27d1dfc commit 938bec2
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,18 @@
</distributionManagement>
<dependencyManagement>
<dependencies>
<!-- This is a workaround for https://github.com/quarkusio/quarkus/issues/42656. Generally, as long as we
go on testing upstream Quarkus with versions of framework compiled and based on already released Quarkus,
possibility of binary incompatibility is high - at least for fabric8 client. This workaround allows us to
bypass using the client managed by Quarkus and just set the client version with the framework.
-->
<dependency>
<groupId>io.fabric8</groupId>
<artifactId>kubernetes-client-bom</artifactId>
<version>6.13.3</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
Expand Down

0 comments on commit 938bec2

Please sign in to comment.