[
https://issues.apache.org/jira/browse/SLING-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508871#comment-17508871
]
Karl Pauls commented on SLING-11158:
------------------------------------
Yeah, the additional problem is that it gets worse with more than one extension
because they might have their own dependencies. For a while, we tried to work
with embedding and shading everything but that becomes a mess so we gave up and
just have to manage the class path of the launcher - at which point it is
better if it brings its dependencies as well.
> The starter's "Start Sling" instructions don't work with feature launcher
> v1.1.28 or later
> ------------------------------------------------------------------------------------------
>
> Key: SLING-11158
> URL: https://issues.apache.org/jira/browse/SLING-11158
> Project: Sling
> Issue Type: Bug
> Affects Versions: Feature Model Launcher 1.1.28, Feature Model Launcher
> 1.2.0
> Reporter: Eric Norman
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.4, Starter 13
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> After the SLING-10956 changes, launching the Starter with the README provided
> instructions while using the v1.1.28 or later feature launcher does not work
> anymore.
> For example,
> {noformat}
> $ java -jar target/dependency/org.apache.sling.feature.launcher.jar -f
> target/slingfeature-tmp/feature-oak_tar.json
> Error: Unable to initialize main class
> org.apache.sling.feature.launcher.impl.Main
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/commons/cli/ParseException{noformat}
>
> Also, the start goal of the feature-launcher-maven-plugin fails with the same
> exception when paired with a featureLauncherVersion of 1.1.28 or later.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
