We discussed it, and I think @Ladicek fixed it, but in case we have done, opening this issue, to make sure we do it and it appears in the release notes.
In section https://jakarta.ee/specifications/cdi/4.0/jakarta-cdi-spec-4.0.html#bean_discovery_steps_full the bullet list links to <> but the link is actually wrong because there is another section for enabled beans in CDI Full mode.
So there is a mismatch. If you strictly read and follow the link, enabled beans do not take Specialized beans into account. The TCK is currently testing them and there is a definition in the document to amend the enabled beans definition in the context of CDI Full.
We discussed it, and I think @Ladicek fixed it, but in case we have done, opening this issue, to make sure we do it and it appears in the release notes.
In section https://jakarta.ee/specifications/cdi/4.0/jakarta-cdi-spec-4.0.html#bean_discovery_steps_full the bullet list links to <> but the link is actually wrong because there is another section for enabled beans in CDI Full mode.
So there is a mismatch. If you strictly read and follow the link, enabled beans do not take Specialized beans into account. The TCK is currently testing them and there is a definition in the document to amend the enabled beans definition in the context of CDI Full.