anchor.diff:  file, and it is used to setup an appropriate `URLClassLoader` and ultimately call your
   `main()` method.
   
  -There are three launcher subclasses (`JarLauncher`, `WarLauncher`, and `PropertiesLauncher`).
  -Their purpose is to load resources (`.class` files and so on.) from nested jar files or war
  -files in directories (as opposed to those explicitly on the classpath). In the case of
  -`JarLauncher` and `WarLauncher`, the nested paths are fixed. `JarLauncher` looks in
  -`BOOT-INF/lib/`, and `WarLauncher` looks in `WEB-INF/lib/` and `WEB-INF/lib-provided/`.
  -You can add extra jars in those locations if you want more. The `PropertiesLauncher`
  -looks in `BOOT-INF/lib/` in your application archive by default, but you can add
  -additional locations by setting an environment variable called `LOADER_PATH` or `loader.path`
  -in `loader.properties` (which is a comma-separated list of directories, archives, or directories
  -within archives).
  +There are three launcher subclasses (`JarLauncher`, `WarLauncher`, and
  +`PropertiesLauncher`). Their purpose is to load resources (`.class` files and so on.) from
  +nested jar files or war files in directories (as opposed to those explicitly on the
  +classpath). In the case of `JarLauncher` and `WarLauncher`, the nested paths are fixed.
  +`JarLauncher` looks in `BOOT-INF/lib/`, and `WarLauncher` looks in `WEB-INF/lib/` and
  +`WEB-INF/lib-provided/`. You can add extra jars in those locations if you want more. The
  +`PropertiesLauncher` looks in `BOOT-INF/lib/` in your application archive by default, but
  +you can add additional locations by setting an environment variable called `LOADER_PATH`
  +or `loader.path` in `loader.properties` (which is a comma-separated list of directories,
  +archives, or directories within archives).
   
   
   
  
positive.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}`.
  
negative.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]
  