[
https://issues.apache.org/jira/browse/SLING-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301005#comment-17301005
]
Karl Pauls commented on SLING-10213:
------------------------------------
I think we'd have to be careful not to make this too much like
meta-programming. However, if we consider this, it might make sense to do it in
the context of the already existing ExecutionEnvironmentExtension [0].
[0]
https://github.com/apache/sling-org-apache-sling-feature/blob/master/src/main/java/org/apache/sling/feature/ExecutionEnvironmentExtension.java
> Feature-Launcher: Add Extensions to Classpath
> ----------------------------------------------
>
> Key: SLING-10213
> URL: https://issues.apache.org/jira/browse/SLING-10213
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model
> Reporter: Stefan Bischof
> Priority: Major
>
> In this
> [PR|https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/18]
> about the docker container SlingFeatureLauncher of
> @karlpauls came up with this:
> in general, it be good if there was a way to add extension jars to the class
> path. We need them for both, merge handlers as well as launcher extensions.
> I'm not sure what the best way would be - maybe somehow (deep search) find
> all jars in a well known location so that one could selectively mount in
> extensions?
> From my point of view it would be nice to have the mecanism that works same
> in docker and default java launcher.
> What do you think about an ExtentionInstaller-Extension? So we can hold
> everything in the Feature-file and load the extensions like every other
> Artefact?
> Here is an example:
> https://github.com/apache/sling-org-apache-sling-feature-launcher/compare/master...stbischof:extensionInstaller
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
