Avoid "Failed to index" warnings produced during @SecureField annotation detection

[michalvavrik]

fixes: #40153

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit f473250.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f473250.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[geoand]

Thanks a lot!

[vmuzikar]

@michalvavrik @gsmet Will this get backported to 3.8?

[michalvavrik]

@michalvavrik @gsmet Will this get backported to 3.8?

I've added a backport label, let's see how it gets accepted.

[rsvoboda]

There is QUARKUS-4431 request on product side.

@vmuzikar this fix was included in Quarkus 3.10.1 released ~1 hour ago, so this doesn't have any bake time.
Is this a must-have for 3.8.5 or would it be ok to wait till 3.8.6 to get community feedback?

[vmuzikar]

@rsvoboda If you are not comfortable with including it last minute in 3.8.5, that's fine for Keycloak. What is the estimated time frame for 3.8.6? Based on that we'll filter the messages on our end.

[rsvoboda]

Bits are out now and it's usually week or two to get feedback in case something goes wrong.

So assuming we are not under immediate pressure to get 3.8.5 out, we could include this in the last 3.8.5 backports round.

[vmuzikar]

Ok, 3.8.5 would be awesome. :)