You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2019/05/07 15:35:00 UTC

[jira] [Resolved] (SLING-8406) Allow the app class path of the feature launcher to be extended by URLs and allow the launcher extension to provide a classloader implementation

     [ https://issues.apache.org/jira/browse/SLING-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved SLING-8406.
-------------------------------
    Resolution: Fixed

Done in 

c5de9e4..b957b3e

> Allow the app class path of the feature launcher to be extended by URLs and allow the launcher extension to provide a classloader implementation
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-8406
>                 URL: https://issues.apache.org/jira/browse/SLING-8406
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model Launcher 1.0.0
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Feature Model Launcher 1.0.2
>
>
> The Feature Model Launcher should allow the launcher to add app jars as urls (besides the existing way of adding them as files). Furthermore, it should be possible to provide a custom classloader for the actual load to allow for scenarios where a specific classloader needs to be used. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)