[
https://issues.apache.org/jira/browse/SLING-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632836#comment-14632836
]
Alex Parvulescu commented on SLING-4478:
----------------------------------------
bq. If you depend on a service defined in org.apache.sling.launchpad.api
makes sense, but _I_ don't directly depend on this, it was pulled in via the
run mode support changes in the file installer (aka. file installer 1.1.0). my
point was that this is a change in behavior, if I'm not using any of the
launchpads.
so to sum it up: to be able to use the file installer 1.1.0 you have to either
use the launchpad or write a custom _StartupHandler_, if this makes sense, then
it should probably end up on the docs page of both the _file installer_ &
_sling settings_.
> Support run modes
> -----------------
>
> Key: SLING-4478
> URL: https://issues.apache.org/jira/browse/SLING-4478
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: File Installer 1.1.0
>
>
> The file installer currently does not support run modes, everything within an
> install folder is installed.
> We could support run modes by checking whether artifacts are in a folder. If
> the folder name follows the pattern install.{runModes} where runModes is the
> set of run modes separated by a dot, we only activate these artifacts if all
> run modes are active.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
