Use Dev Services for Infinispan Client IT and enforce Hibernate Search constraint in BOM

[gsmet]

Dragging the server via a test resource was problematic as the server requires a specific version of Hibernate Search.
Now that we have Dev Services for Infinispan, we can use them in the Infinispan IT module.

[yrodiere]

So this was really just the test setup, there is no backwards incompatibility caused by the Search 6.0 => 6.1 upgrade at all in the end.

Thanks for taking care of this, @gsmet!

[karesti]

Changes look good to me! thanks @gsmet

[karesti]

Sorry I just saw this error on the HealthCheck

java.lang.RuntimeException:
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[error]: Build step io.quarkus.infinispan.client.deployment.devservices.InfinispanDevServiceProcessor#startInfinispanContainers threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerFetchException: Can't get Docker image

is

[karesti]

@gsmet the code is ok but I'm just wondering what happened with the healthcheck test that failed and if is just normal

[aloubyansky]

@karesti if you are curious about the original issue, it was found that (a part of) Infinispan was incompatible with Hibernate Search included in Quarkus #26565 (comment)
This PR is a workaround to avoid using the Infinispan server and Hibernate Search in the same runtime for the test.

[gsmet]

Issue fixed, let's wait for CI.

[quarkus-bot]

Failing Jobs - Building e647753

Status	Name	Step	Failures	Logs	Raw logs
✔️	Gradle Tests - JDK 11
✖	Gradle Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
⌛	JVM Tests - JDK 18	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

✖ io.quarkus.gradle.devmode.QuarkusDevDependencyDevModeTest.main line 14 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

---

⚙️ JVM Tests - JDK 18 #

- Failing: extensions/hibernate-search-orm-elasticsearch/deployment integration-tests/elasticsearch-rest-client integration-tests/elasticsearch-rest-high-level-client and 1 more
! Skipped: extensions/hibernate-search-orm-coordination-outbox-polling/deployment integration-tests/devmode integration-tests/hibernate-search-orm-elasticsearch and 3 more

📦 extensions/hibernate-search-orm-elasticsearch/deployment

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.40.1:start (docker-start) on project quarkus-hibernate-search-orm-elasticsearch-deployment: I/O Error

📦 integration-tests/elasticsearch-rest-client

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.40.1:start (docker-start) on project quarkus-integration-test-elasticsearch-rest-client: I/O Error

📦 integration-tests/elasticsearch-rest-high-level-client

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.40.1:start (docker-start) on project quarkus-integration-test-elasticsearch-rest-high-level-client: I/O Error

📦 integration-tests/logging-gelf

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.40.1:start (docker-start) on project quarkus-integration-test-logging-gelf: I/O Error