Robert Munteanu created SLING-9993:
--------------------------------------
Summary: Allow configuring extensions using the CLI
Key: SLING-9993
URL: https://issues.apache.org/jira/browse/SLING-9993
Project: Sling
Issue Type: New Feature
Components: Feature Model
Reporter: Robert Munteanu
Fix For: Feature Model Launcher 1.1.16
When switching from using just the launcher to using the launcher + extensions
the launch command becomes more convoluted. Compare:
{noformat}
$ java -jar target/dependency/org.apache.sling.feature.launcher.jar
{noformat}
with
{noformat}
$ java -cp
target/dependency/org.apache.sling.feature.launcher.jar:target/dependency/some.extension.jar
org.apache.sling.feature.launcher.impl.Main
{noformat}
It would be very useful to be able to specify extensions as CLI arguments, e.g.
{noformat}
$ java -jar target/dependency/org.apache.sling.feature.launcher.jar -e
target/dependency/some.extension.jar
{noformat}
or maybe an extension directory
{noformat}
$ java -jar target/dependency/org.apache.sling.feature.launcher.jar -ed
target/dependency/extensions
{noformat}
We could even go as far as automatically loading extensions from a
{{LAUNCHER_HOME/ext}} directory ( with proper logging, of course ).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
