anchor.diff:  	 0063                 3452        3980
   ----
   
  -The preceding example shows how `A.class` can be found in `/BOOT-INF/classes` in `myapp.jar`
  -at position `0063`. `B.class` from the nested jar can actually be found in `myapp.jar`
  -at position `3452`, and `C.class` is at position `3980`.
  +The preceding example shows how `A.class` can be found in `/BOOT-INF/classes` in
  +`myapp.jar` at position `0063`. `B.class` from the nested jar can actually be found in
  +`myapp.jar` at position `3452`, and `C.class` is at position `3980`.
   
   Armed with this information, we can load specific nested entries by seeking to
   the appropriate part of the outer jar. We do not need to unpack the archive, and we
  
positive.code: 
  [[executable-jar-alternatives]]
  === Alternative Single Jar Solutions
  If the preceding restrictions mean that you cannot use Spring Boot Loader, consider the following
  alternatives:
  
  * http://maven.apache.org/plugins/maven-shade-plugin/[Maven Shade Plugin]
  * http://www.jdotsoft.com/JarClassLoader.php[JarClassLoader]
  
negative.code: |Key |Purpose
  
  |`loader.path`
  |Comma-separated Classpath, such as `lib,${HOME}/app/lib`. Earlier entries take
   precedence, like a regular `-classpath` on the `javac` command line.
  
  |`loader.home`
  |Used to resolve relative paths in `loader.path`. For example, given `loader.path=lib`,
   then `${loader.home}/lib` is a classpath location (along with all jar files in that
   directory). This property is also used to locate a `loader.properties` file, as in the
   following example `file:///opt/app`
   It defaults to `${user.dir}`.
  