anchor.diff:      <main.class>com.foo.Application</main.class>
   </properties>
   ----
  -
  -If you want to avoid inheriting from the framework parent pom, you will need to explicitly provide the following unwieldy configuration similar to the one found in https://repo1.maven.org/maven2/io/bootique/parent/bootique-parent/0.12/bootique-parent-0.12.pom[`bootique-parent`]:
  +If you don't want inherit from the framework pom, you will need to explicitly provide the following (fairly long)
  +configuration similar to the one found in
  +https://repo1.maven.org/maven2/io/bootique/parent/bootique-parent/0.14/bootique-parent-0.14.pom[`bootique-parent`]:
   
   [source,xml]
   ----
  
positive.code: java -jar target/myapp-1.0.jar
  ----
  
  === Tracing Bootique Startup
  
  To see what modules are loaded, to view full app configuration tree and to trace other events that happen on startup, run your app with `-Dbq.trace` option. E.g.:
  
negative.code: 
  == Part IV. Assembly and Deployment
  
  Since every Bootique app contains a `main(..)` method, it can be executed using `java` command. Here we are going to
  discuss two common cross-platform approaches - "<<runnable-jar-with-dependencies,Runnable Jar with Dependencies>>" and
  "<<runnable-jar-with-lib,Runnable Jar with "lib" Folder>>" that differ in how dependencies are packaged and referenced.
  
  Another way to package apps (not discussed here) is creating native binaries with
  https://docs.oracle.com/en/java/javase/12/tools/jlink.html[jlink] or https://www.graalvm.org/[GraalVM] (since Bootique
  2.0).
  
  [#runnable-jar-with-dependencies]
  === Runnable Jar with Dependencies
  
  This approach packages application classes (and resources) and all the dependencies in a single "fat" runnable jar. In
  Maven this can be accomplished with `maven-shade-plugin`. To simplify plugin configuration, your app `pom.xml` may
  inherit from `bootique-parent` pom. In this case configuration would look like this:
  
  [source,xml,subs="attributes"]
  ----
  