[
https://issues.apache.org/jira/browse/SLING-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-11408:
------------------------------------
Description: 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. (was: For the standalone usecase cp2fm 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.)
> Make sure that feature launcher contains all 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: Content-Package to Feature Model Converter 1.1.16
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> 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.7#820007)
