anchor.diff:  the bytecode metadata for wiring up components instead of angle-bracket declarations.
   Instead of using XML to describe a bean wiring, the developer moves the configuration
   into the component class itself by using annotations on the relevant class, method, or
  -field declaration. As mentioned in <<beans-factory-extension-bpp-examples-rabpp>>, using
  +field declaration. As mentioned in <<beans-factory-extension-bpp-examples-aabpp>>, using
   a `BeanPostProcessor` in conjunction with annotations is a common means of extending the
   Spring IoC container. For example, Spring 2.0 introduced the possibility of enforcing
   required properties with the <<beans-required-annotation,`@Required`>> annotation. Spring
  
positive.code: 
  [NOTE]
  ====
  The `@Required` annotation is formally deprecated as of Spring Framework 5.1, in favor
  of using constructor injection for required settings (or a custom implementation of
  `InitializingBean.afterPropertiesSet()` along with bean property setter methods).
  ====
  
  
  
negative.code: }
  ----
  
  This annotation indicates that the affected bean property must be populated at
  configuration time, through an explicit property value in a bean definition or through
  autowiring. The container throws an exception if the affected bean property has not been
  