-
Notifications
You must be signed in to change notification settings - Fork 219
Closed
Labels
for: eclipsesomething that is specific for Eclipsesomething that is specific for Eclipsefor: vscodesomething that is specific for VSCodesomething that is specific for VSCodestatus: needs-investigationtheme: internal-architecturetype: bug
Milestone
Description
Java file with class A is definition of an annotation that is annotated with @Configuration
Java file with class B annotated with A has bean definitions.
Once @Configuration
is removed from A and saved it is expected that B has a warning about missing @Configuration
. However, nothing happens. Even after editing B.
The issue is that classpath is considered not to be changed. Therefore java parser isn't reset and still based on old implementation of everything. If project is closed and re-opened (or IDE restarted or reloaded) then B class would have proper warning.
This issue has been around for a long time.
Metadata
Metadata
Assignees
Labels
for: eclipsesomething that is specific for Eclipsesomething that is specific for Eclipsefor: vscodesomething that is specific for VSCodesomething that is specific for VSCodestatus: needs-investigationtheme: internal-architecturetype: bug