|
I understand. The use case is for CDI extension that must be compatible with CDI 1.0. For example, the Camel CDI extension has been made explicitly compatible with CDI 1.0 by removing the @WithAnnotations use as it's not available in CDI 1.0 only environments like JBoss EAP 6. The problem is that users on newer environments get that message and there is no action they can perform. They get the message even with CDI 1.2, Weld 2.3.3.Final.
So it's down to the extension developer, which (in my case ) is aware of the drawback of using ProcessAnnotatedType lifecycle observer methods whose types is unbounded wildcard or Object. So that ideally there would be a way for him to explicitly acknowledge that and avoid end-users asking about that message (as they do ) while there is no solution.
Maybe one solution would be to check if the version attribute of the beans.xml descriptor is set to 1.0 and not log the message in that case: https://github.com/apache/camel/blob/4e13eae10a6fcb30846e786bc76b78f3f1fcbfb8/components/camel-cdi/src/main/resources/META-INF/beans.xml#L18
|