OpenAPI Filters ensure consistent ordering

[melloware]

Based on Zulip: #dev > OpenAPI Filter enforce order with priority in extensions @ 💬

And open Quarkus Logging manager ticket: quarkiverse/quarkus-logging-manager#373

this uses the classnames to always ensure the same order when generating from OASFilters like SmallRye Health, RestEasyProblem, and Logging Manager

[gastaldi]

/cc @MikeEdgar

[melloware]

@MikeEdgar i realized its all extensions thta produce AddToOpenAPIDefinitionBuildItem not ones marked with @OpenApiFilter so this one is picking up all produced build items and then flickering I guess depending on the build order.

[MikeEdgar]

@MikeEdgar i realized its all extensions thta produce AddToOpenAPIDefinitionBuildItem not ones marked with @OpenApiFilter so this one is picking up all produced build items and then flickering I guess depending on the build order.

So the issue could still occur for user filters with equal priorities in @OpenApiFilter and this just addresses extensions using the build item - got it. Thanks

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ 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.