[JBIDE-18964] Changing bean discovery mode doesn't run validation for existing beans - Red Hat Issue Tracker

Steps to Reproduce:

Hide

1. Create CDI 1.1 project with discovery mode annotated
2. Create two java classes (ie Bean1 and Bean2)
3. add scope to Bean1 and inject Bean2
ASSERT: warning is shown "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]"

4. change discovery mode to all
ASSERT: no warning is displayed in Bean1
FAIL: warning is still present. You have to edit Bean1 to reflect new discovery mode.

NOTE: This applies for all beans - if you have more, you have to edit all of them (or run validate)

Show
1. Create CDI 1.1 project with discovery mode annotated 2. Create two java classes (ie Bean1 and Bean2) 3. add scope to Bean1 and inject Bean2 ASSERT: warning is shown "No bean is eligible for injection to the injection point [JSR-299 §5.2.1] " 4. change discovery mode to all ASSERT: no warning is displayed in Bean1 FAIL: warning is still present. You have to edit Bean1 to reflect new discovery mode. NOTE: This applies for all beans - if you have more, you have to edit all of them (or run validate)
Workaround:

Workaround Exists
Workaround Description:

Hide

run validate or edit bean

Show
run validate or edit bean
Git Pull Request:
https://github.com/jbosstools/jbosstools-base/pull/363, https://github.com/jbosstools/jbosstools-javaee/pull/281, https://github.com/jbosstools/jbosstools-javaee/pull/309