You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/07/12 14:09:00 UTC
[jira] [Resolved] (SLING-11408) Make sure that feature launcher contains only necessary runtime dependencies
[ https://issues.apache.org/jira/browse/SLING-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-11408.
-------------------------------------
Resolution: Fixed
Fixed in https://github.com/apache/sling-org-apache-sling-feature-launcher/commit/fac1d00fe08130a7857bc78d1b1de7b82e1e9818.
> 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)