[SLING-10213] Feature-Launcher: Add Extensions to Classpath

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Feature Model
• Assignee: Unassigned
• Reporter: Stefan Bischof
• Created: 13/Mar/21 21:30
• Updated: 20/Apr/21 10:01

Description

In this PR 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