[
https://issues.apache.org/jira/browse/SLING-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632830#comment-14632830
]
Alex Parvulescu commented on SLING-4478:
----------------------------------------
I understand that I'm only probably representing less than 1% of the user base
here so take the following (rant) with a grain of salt :)
I'm only trying to use the file installer features, then notice that the new
version comes with a few new dependencies, ok, so far so good, except now this
service _expects_ that there's a _SlingSettingsService_ wired, which is an
_undocumented_ change in behavior, and it doesn't end here: the
_SlingSettingsService_ expects a _StartupHandler_ service to be available,
otherwise it won't boot! Don't get me wrong, I'm ok with adding new
dependencies, what I'm not happy with is having to write custom code just to
make sure some service I might not use starts up.
So right now there's zero ways to install _all_ of these bundles and have
things work they used to :/
bq. I think if you're using an older SlingSettingsService bundle it should do
the trick.
agreed, the same can be said about using an older file installer version :)
> 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)
