[
https://issues.apache.org/jira/browse/SLING-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169730#comment-17169730
]
Carsten Ziegeler commented on SLING-7504:
-----------------------------------------
I don't think that this belongs in the feature model itself. Not sure if the
feature launcher plugin is a good place for this?
At this point it is unclear to me what the use case is? Someone downloading the
starter jar will not run a maven plugin - on the other end if a maven build is
invoked there are plenty ways of letting maven create the directory
> Sling File Installer Provider inactive in Sling Starter
> -------------------------------------------------------
>
> Key: SLING-7504
> URL: https://issues.apache.org/jira/browse/SLING-7504
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Starter 12
>
>
> Even in the newest Starter 11 the framework property for the Sling File
> Installer is not set by default. This should be fixed. The relevant framework
> property is {{sling.fileinstall.dir}}. I propose to set this to
> {{${sling.home}/install}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
