anchor.diff:  public class TracerConfiguration {
   
       @Produces
  -    @DefaultBean
  +    @UnlessBuildProfile("test") // this will be enabled for both prod and dev build time profiles
       public Tracer realTracer(Reporter reporter, Configuration configuration) {
           return new RealTracer(reporter, configuration);
       }
   
       @Produces
  -    @UnlessBuildProfile("prod") // this will be enabled for both test and dev build time profiles
  +    @DefaultBean
       public Tracer noopTracer() {
           return new NoopTracer();
       }
  
positive.code: via the `@io.quarkus.arc.profile.IfBuildProfile` and `@io.quarkus.arc.profile.UnlessBuildProfile` annotations.
  When used in conjunction with `@io.quarkus.arc.DefaultBean`, these annotations allow for the creation of different bean configurations for different build profiles.
  
  Imagine for instance that an application contains a bean named `Tracer`, which needs to be do nothing when in tests or dev-mode, but work in its normal capacity for the production artifact.
  An elegant way to create such beans is the following:
  
  [source,java]
  
negative.code: }
  ----
  
  If instead, it is required that the `Tracer` bean also works in dev-mode and only default to doing nothing for tests, then `@UnlessBuildProfile` would be ideal. The code would look like:
  
  [source,java]
  ----
  