[
https://issues.apache.org/jira/browse/SLING-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575223#comment-17575223
]
Carsten Ziegeler commented on SLING-11408:
------------------------------------------
I already commented on the PR, but for completeness again here:
PR fixes one part, but there are now additional problems:
1. slf4j-impl is missing
2. the launch script now lists all jar files from lib as the classpath, whereas
previously a wildcard was used (lib/*), which allowed to just add new jars in
the libs directory
> Make sure that feature launcher contains only necessary runtime dependencies
> ----------------------------------------------------------------------------
>
> Key: SLING-11408
> URL: https://issues.apache.org/jira/browse/SLING-11408
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Feature Model Launcher 1.2.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Feature Model Launcher 1.2.2
>
>
> Feature Launcher uses {{appassembler-maven-plugin}} for packaging all runtime
> dependencies into the classpath. As a lot of required dependencies have scope
> "provided" (due to primary usage within OSGi) it is hard to come up with a
> correct runtime classpath. The enforcer rule from SLING-11369 should be
> leveraged to automatically enforce a complete runtime classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
