OpenAPI: auto-add-tags feature uses superclass/interface name, rather than actual class name

Describe the bug

Consider the following:

@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public interface AbstractReadOnlyResource<T> {
    @GET
    @Path("/{id}")
    T getById(@PathParam("id") long id);
}

and

@Path("/address")
public class AddressResource implements AbstractReadOnlyResource<Address> {
    @Override
    public Address getById(long id) {
        // Removed for brevity
    }
}

Expected behavior

The get operation of the /address/{id} path is tagged with Address Resource.

Actual behavior

The resource is tagged with Abstract Read Only Resource.

OpenAPI JSON contains

"paths" : {
  "/address/{id}" : {
    "get" : {
      "tags" : [ "Abstract Read Only Resource" ],
      "parameters" : [ {
        "name" : "id",
        "in" : "path",
        "required" : true,
        "schema" : {
          "format" : "int64",
          "type" : "integer"
        }
      } ],
    }
  }
}

Swagger UI shows:

How to Reproduce?

~Will add a link to a GitHub repo shortly.~

EDIT: A small reproducer project can be found here.

Output of uname -a or ver

Linux jbe-desktop 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Output of java -version

openjdk version “11.0.11” 2021-04-20

GraalVM version (if different from Java)

none

Quarkus version or git rev

2.4.0.Final

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.8.3 (ff8e977a158738155dc465c6a97ffaf31982d739)

Additional information

No response

[phillip-kruger]

Thanks @MikeEdgar !

[j-be]

@phillip-kruger that is excellent news! thank you very much, looking forward to the release 😄