anchor.diff:  ----
   <1> Note that there is no @Inject qualifier here. This is a feature of the CDI implementation used by the Shamrock core to process @ConfigProperty only available to the deployment time extension.
   
  -The value of these properties is configured in a META-INF/microprofile-config.properties file that conforms to the MicroProfile config format.
  +The value of these properties is configured in a `META-INF/microprofile-config.properties` file that conforms to the MicroProfile config format.
   
   An extension of MicroProfile config to allow configuration objects to be injected is available using the `@org.jboss.shamrock.runtime.ConfigGroup` annotation. You place this annotation on the configuration object which in turn uses @ConfigProperty for it's configurable values as follows:
   
  
positive.code: object at runtime.
  
  In more detail, a processor class from the extensions deployment module gathers the configuration
  information within a @BuildStep` method that is also annotated with a `@Record(STATIC_INIT)` or  `@Record(RUNTIME_INIT)` annotation along with injection of a `@Template` annotated class
  from the runtime module. A class annotated with `@Template` is known as a template because it
  provides a template of methods to configure a runtime service. The value of template that is
  injected into the deployment class is a proxy of the template, and any method invocations that are made will be recorded, and output as bytecode that will be run at application startup.
  
negative.code: configuration object containing a collection of configurable properties.
  <2> Here the LoggingProcessor injects a FileConfig instance using the MicroProfile Config annotation with the property name "shamrock.log.file". 
  
  A corresponding `META-INF/microprofile-config.properties` file for the FileConfig values could be:
  [source%nowrap,properties]
  ----
  shamrock.log.file.enable=true
  