ArC - rework the way the build profile/property producer beans are disabled

[mkouba]

Currently, we add @Alternative and remove @AlternativePriority if present. However, if a user declares an @Alternative producer and enables it via quarkus.arc.selected-alternatives then @UnlessBuildProperty and friends would have no effect.

We could:

1. Remove @Produces and all scopes and known qualifiers/stereotypes (due to Simplified Producer Method Declaration),
2. Remove all annotations (just in the context of AnnotationStore),
3. Introduce a new annotation, e.g. @VetoedProducer (note that @javax.enterprise.inject.Vetoed has @Target({ ElementType.TYPE, ElementType.PACKAGE })).

[quarkus-bot]

/cc @manovotn

[manovotn]

Introduce a new annotation, e.g. @VetoedProducer (note that @javax.enterprise.inject.Vetoed has @target({ ElementType.TYPE, ElementType.PACKAGE })).

A bit outside of this question but do you think it would be worth it to expand CDI spec to allow usage of @Vetoed on methods/fields? I think it might be worth it.

Otherwise, option 3 sounds like a way to go.

[mkouba]

A bit outside of this question but do you think it would be worth it to expand CDI spec to allow usage of @Vetoed on methods/fields? I think it might be worth it.

I'm not sure TBH. The original intent of @Vetoed was probably to exclude classes from an explicit bean archive (bean discovery all), i.e. those that would otherwise end up as @Dependent beans. For sure you can use it for tests etc. but the majority of use cases was probably different. See also https://issues.redhat.com/browse/CDI-50.