anchor.diff:  |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.
  +|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
  +|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}`.
  
positive.code: 	 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`.
  
  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
  
negative.code: 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).
  
  
  
  