commit | 04e18bd324d243d35647abbac3eb65620c5dd007 | [log] [tgz] |
---|---|---|
author | David Bosschaert <bosschae@adobe.com> | Fri Jun 25 10:17:37 2021 +0100 |
committer | David Bosschaert <bosschae@adobe.com> | Fri Jun 25 10:17:37 2021 +0100 |
tree | 88761cb948c54fd2e49b5ceebe048fd4ddca5c43 | |
parent | 0190cf08f5be7b5af84cf237c9439c5170d86063 [diff] |
Update dependencies
The Feature Model Launcher can launch an feature model application file to a running process.
The launcher can be executed as follows:
java org.apache.sling.feature.launcher.impl.Main
or via the Java Main class of the jar file:
java -jar org.apache.sling.feature.launcher.jar
The launcher creates a local cache, by default in a subdirectory called launcher
. If you want to run the launcher with a clean start, delete this directory before invoking the launcher.
The following command line options are supported:
$ rm -rf launcher && java -jar org.apache.sling.feature.launcher.jar -h usage: launcher -C <arg> Set artifact clash override -CC <arg> Set config class override -c <arg> Set cache dir -D <arg> Set framework properties -f <arg> Set feature files (relative and absolute file path or URL including classloader resources) -p <arg> Set home dir -u <arg> Set repository url -V <arg> Set variable value -ec <arg> Set Extension Configuration (format: extensionName:key1=val1,key2=val2) -fv <arg> Set Felix Framework version -fa <arg> Set Framework Artifact (overrides felix framework version) -v Verbose
Note: if feature files are provided as a Classloader Resource like in an executable JAR file or classpath resource then it's Resource URL can be handed over to the Launcher as feature file (-f option):
java.net.URL url = getClass().getResource("/my-feature-file.json"); String[] arguments = new String[] { "-f", url.toString() }; org.apache.sling.feature.launcher.impl.Main.main(arguments);
For further documentation see: https://github.com/apache/sling-org-apache-sling-feature/blob/master/readme.md