Upgrade to Hibernate Search 6.2.0.Final

[yrodiere]

Changes since 6.2.0.CR1: https://hibernate.atlassian.net/issues/?jql=project=10061+AND+fixVersion=32168

There weren't many changes. Just a few micro dependency upgrades.

[quarkus-bot]

/cc @gsmet (hibernate-search)

[gsmet]

LGTM but I need to restart CI as all the builds failed.

[Sanne]

Rebased, not least to trigger another CI run

[Sanne]

It would seem none of the windows builds were able to complete. I can't say for sure but I haven't seen other recent PRs fail for a similar reason so it's a bit suspicious...

@marko-bekhta would you be able to have a better look?

[marko-bekhta]

Ohh windows 😈 let me check what I can do 😃

[Sanne]

@marko-bekhta thanks! But before digging deep, try to see if there were other PRs with the same issue - I don't know for sure if it's really the fault of this pr.

[marko-bekhta]

But before digging deep

Ouch 😨😢 should've read that before installing windows 😆😆😆.

Just joking, I had a windows env but it didn't have quarkus on it so I've tried to build there -- but for some reason, it takes ages just to even run ./mvnw -Dquickly

From what I see the failed KotlinProjectWithCompilerArgsDevModeTest test is trying to do something with kotlin-grpc-project and there's nothing related to Search so I'd assume it is not related to the upgrade 😃

I see that a few neighbouring PRs have the timeouts on windows builds too...

There also don't seem to be any obvious changes in this release compared to CR1 that would cause any issues.

Maybe it's worth to try and restart the build once more? 🙈

[Sanne]

great, thanks @marko-bekhta - I've now triggered a fresh build, let's see how it goes.

[gsmet]

I rebased and force pushed to fix a conflict.

[quarkus-bot]

Failing Jobs - Building 69fe7f5

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 19
✔️	Maven Tests - JDK 11
⌛	Maven Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/vertx-http/deployment 
! Skipped: extensions/agroal/deployment extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 351 more

📦 extensions/vertx-http/deployment

✖ io.quarkus.vertx.http.testrunner.tags.IncludeTagsTestCase.checkTestsAreRun line 52 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run 2 State{lastRun=1, running=true, inProgress=true, run=2, passed=2, failed=0, skipped=0, isBrokenOnly=false, isTestOutput=false, isInstrumentationBasedReload=false, isLiveReload=true}
	at io.quarkus.test.ContinuousTestingTestUtils.waitForNextCompletion(ContinuousTestingTestUtils.java:44)
	at io.quarkus.vertx.http.testrunner.tags.IncludeTagsTestCase.checkTestsAreRun(IncludeTagsTestCase.java:52)

[gsmet]

I'm not entirely sure if @yrodiere wanted a backport so I will wait for him to come back.