Build fails for @Provider exception mapper

starting with 0.23.2 I get [ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:0.25.0:build (default) on project demo: Failed to build a runnable JAR: Failed to build a runner jar: Failed to augment application classes: Build failure: Build failed due to errors [ERROR] [error]: Build step io.quarkus.arc.deployment.ArcProcessor#registerBeans threw an exception: javax.enterprise.inject.spi.DefinitionException: Bean class com.demo.excmapper.IllegalArgumentExceptionMapper declares multiple scope type annotations: javax.enterprise.context.Dependent, javax.inject.Singleton

Steps to reproduce the behavior:

1. Create sample hello project
2. Add the class

import org.eclipse.microprofile.metrics.Counter;
import org.eclipse.microprofile.metrics.annotation.Metric;

import javax.inject.Inject;

import javax.ws.rs.core.Response;
import javax.ws.rs.ext.ExceptionMapper;
import javax.ws.rs.ext.Provider;

@Provider
public class IllegalArgumentExceptionMapper implements ExceptionMapper<IllegalArgumentException> {
   
    @Inject
    @Metric(absolute = true, name = "error_count", description = "count", displayName = "error_count")
    private Counter counter;

    @Override
    public Response toResponse(IllegalArgumentException exception) {
        counter.inc();
        return Response.status(500).entity("illegal").build();
    }
}

1. run mvn package getting-started.zip

[jmartisk]

Oh, now I get it, so we’ll make the Metrics AnnotationsTransformer run after the one for Resteasy, and also when checking whether there is a scope present already, instead of doing BuiltinScope.isDeclaredOn(ctx.getTarget().asClass()), we will do BuiltinScope.isIn(ctx.getAnnotations()) (so it will see scopes added by other transformers), does that sound good?

I guess we could then discard the checks (in the Metrics transformer) whether the bean is a JAX-RS endpoint/provider, but for being extra safe I would maybe keep them… (?)

[gsmet]

Fixed by https://github.com/quarkusio/quarkus/pull/4688 .