[ 
https://issues.apache.org/jira/browse/SLING-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575207#comment-17575207
 ] 

Konrad Windszus edited comment on SLING-11408 at 8/4/22 11:02 AM:
------------------------------------------------------------------

Ok, the m-assembler-p is configured really wrong here (contributed in 
SLING-10956). Should be fixed by 
https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/42.


was (Author: kwin):
Ok, the m-assembler-p is configured really wrong here. Should be fixed by 
https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/42.

> 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)

Reply via email to