Thanks, Jozef Hartinger. That makes sense...

From my perspective as an app developer, many frameworks spit out warnings if anything is seemingly incorrect because many of us disable anything below WARNING level for development because it's so noisy.

I understand that Weld can't distinguish between (1) and (2), so to my untrained eye, that's an argument in favor of always spitting out a WARNING, if not out-right failing. I understand the CDI spec plays into your decision making, so perhaps a Weld-specific @Mandatory annotation would be useful?

Just for the record, my use case is (1), it's a hard dependency on LicenseAgreementManager, so I was definitely expecting a deployment failure instead of an INFO log.