anchor.diff:  ----
   // Starting the app with "--my-opt" is equivalent to starting with "--config=classpath:xyz.yml"
   BQCoreModule.extend(binder)
  -        .addOption(OptionMetaData.buidler("my-opt").build())
  +        .addOption(OptionMetaData.builder("my-opt").build())
           .mapConfigResource("my-opt", "classpath:xyz.yml");
   ----
   
  
positive.code: 
  While not strictly required, as a rule the top-level keys in the file belong to configuration objects of individual modules. In the example above "log" subtree configures `bootique-logback` module, while "jetty" subtree configures `bootique-jetty`. For standard modules refer to module-specific documentation on the structure of the supported configuration (or run your app `-H` flag to print supported config to the console). Here we'll discuss how to build your own configuration-aware module.
  
  Bootique allows each Module to read its specific configuration subree as an object of the type defined in the Module. Very often such an object is written as a factory that contains a bunch of setters for configuration properties, and a factory method to produce some "service" that a Module is interested in. Here is an example factory:
  
  [source,java]
  ----
  
negative.code: ----
  // Starting the app with "--my-opt=x" will set "jobs.myjob.param" value to "x"
  BQCoreModule.extend(binder)
          .addOption(OptionMetaData.builder("my-opt").build())
          .mapConfigPath("my-opt", "jobs.myjob.param");
  ----
  . Option presence sets a property to a predefined value:
  