Skip to content

Commit

Permalink
Make REST Assured version available in the build
Browse files Browse the repository at this point in the history
It is actually used (but missing!) when we build the platform
descriptor.
Moving it to the parent POM to be available everywhere.
  • Loading branch information
gsmet committed Apr 11, 2024
1 parent 0bbbfdc commit 1fd3f8c
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 1 deletion.
1 change: 0 additions & 1 deletion bom/application/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,6 @@
<derby-jdbc.version>10.14.2.0</derby-jdbc.version>
<db2-jdbc.version>11.5.8.0</db2-jdbc.version>
<shrinkwrap.version>1.2.6</shrinkwrap.version>
<rest-assured.version>5.4.0</rest-assured.version>
<hamcrest.version>2.2</hamcrest.version><!-- The version needs to be compatible with both REST Assured and Awaitility -->
<junit.jupiter.version>5.10.2</junit.jupiter.version>
<infinispan.version>15.0.0.Final</infinispan.version>
Expand Down
1 change: 1 addition & 0 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,7 @@
<!-- Dependency versions -->
<jacoco.version>0.8.12</jacoco.version>
<kubernetes-client.version>6.11.0</kubernetes-client.version> <!-- Please check with Java Operator SDK team before updating -->
<rest-assured.version>5.4.0</rest-assured.version>

<!-- Make sure to check compatibility between these 2 gRPC components before upgrade -->
<grpc.version>1.62.2</grpc.version> <!-- when updating, verify if com.google.auth should not be updated too -->
Expand Down

0 comments on commit 1fd3f8c

Please sign in to comment.