|
|
|
|
@ -200,12 +200,12 @@ the appropriate launcher:
@@ -200,12 +200,12 @@ the appropriate launcher:
|
|
|
|
|
properties (System properties, environment variables, manifest entries or |
|
|
|
|
`application.properties`). |
|
|
|
|
|
|
|
|
|
[cols="2,4"] |
|
|
|
|
|=== |
|
|
|
|
|Key |Purpose |
|
|
|
|
|
|
|
|
|
|`loader.path` |
|
|
|
|
|Comma-separated Classpath, e.g. `lib,${HOME}/app/lib`. Earlier entries take precedence, just like a regular `-classpath` on the `javac` command line. |
|
|
|
|
|Comma-separated Classpath, e.g. `lib,${HOME}/app/lib`. Earlier entries take precedence, |
|
|
|
|
just like a regular `-classpath` on the `javac` command line. |
|
|
|
|
|
|
|
|
|
|`loader.home` |
|
|
|
|
|Location of additional properties file, e.g. `file:///opt/app` |
|
|
|
|
@ -227,25 +227,52 @@ properties (System properties, environment variables, manifest entries or
@@ -227,25 +227,52 @@ properties (System properties, environment variables, manifest entries or
|
|
|
|
|
|`loader.system` |
|
|
|
|
|Boolean flag to indicate that all properties should be added to System properties |
|
|
|
|
(defaults to `false`) |
|
|
|
|
|
|
|
|
|
|=== |
|
|
|
|
|
|
|
|
|
Manifest entry keys are formed by capitalizing initial letters of words and changing the |
|
|
|
|
separator to "`-`" from "`.`" (e.g. `Loader-Path`). The exception is `loader.main` which |
|
|
|
|
is looked up as `Start-Class` in the manifest for compatibility with `JarLauncher`). |
|
|
|
|
When specified as environment variables or manifest entries, the following names should |
|
|
|
|
be used: |
|
|
|
|
|
|
|
|
|
|=== |
|
|
|
|
|Key | Manifest entry | Environment variable |
|
|
|
|
|
|
|
|
|
|`loader.path` |
|
|
|
|
|`Loader-Path` |
|
|
|
|
|`LOADER_PATH` |
|
|
|
|
|
|
|
|
|
|`loader.home` |
|
|
|
|
| |
|
|
|
|
|`LOADER_HOME` |
|
|
|
|
|
|
|
|
|
|`loader.args` |
|
|
|
|
|`Loader-Args` |
|
|
|
|
|`LOADER_ARGS` |
|
|
|
|
|
|
|
|
|
|`loader.main` |
|
|
|
|
|`Start-Class` |
|
|
|
|
|`LOADER_MAIN` |
|
|
|
|
|
|
|
|
|
|`loader.config.location` |
|
|
|
|
| |
|
|
|
|
|`LOADER_CONFIG_LOCATION` |
|
|
|
|
|
|
|
|
|
|`loader.system` |
|
|
|
|
| |
|
|
|
|
|`LOADER_SYSTEM` |
|
|
|
|
|
|
|
|
|
|=== |
|
|
|
|
|
|
|
|
|
TIP: Build plugins automatically move the `Main-Class` attribute to `Start-Class` when |
|
|
|
|
the fat jar is built. If you are using that, specify the name of the class to launch using |
|
|
|
|
the `Main-Class` attribute and leave out `Start-Class`. |
|
|
|
|
|
|
|
|
|
Environment variables can be capitalized with underscore separators instead of periods. |
|
|
|
|
|
|
|
|
|
* `loader.home` is the directory location of an additional properties file (overriding |
|
|
|
|
the default) as long as `loader.config.location` is not specified. |
|
|
|
|
the default) as long as `loader.config.location` is not specified. |
|
|
|
|
* `loader.path` can contain directories (scanned recursively for jar and zip files), |
|
|
|
|
archive paths, or wildcard patterns (for the default JVM behavior). |
|
|
|
|
* `loader.path` (if empty) defaults to `lib` (meaning a local directory or a nested one if |
|
|
|
|
running from an archive). Because of this `PropertiesLauncher` behaves the same as |
|
|
|
|
`JarLauncher` when no additional configuration is provided. |
|
|
|
|
* `loader.path` (if empty) defaults to `BOOT-INF/lib` (meaning a local directory or a |
|
|
|
|
nested one if running from an archive). Because of this `PropertiesLauncher` behaves the |
|
|
|
|
same as `JarLauncher` when no additional configuration is provided. |
|
|
|
|
* Placeholder replacement is done from System and environment variables plus the |
|
|
|
|
properties file itself on all values before use. |
|
|
|
|
|
|
|
|
|
|