anchor.diff:  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:
  +A corresponding `META-INF/microprofile-config.properties` file for the FileConfig values could be:
   [source%nowrap,properties]
   ----
   shamrock.log.file.enable=true
  
positive.code: == Maven setup
  
  Your extension project should be setup as a multi-module project with two submodules:
  1. A deployment time submodule that handles the build time processing and bytecode recording.
  2. A runtime submodule that contains the runtime behavior that will provide the exentsion behavior in the native image or runtime JVM.
  
  Your runtime artifact should depend on shamrock-core-runtime, and possibly the runtime artifacts of other Shamrock
  
negative.code: ----
  <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.
  
  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:
  
  