[
https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409333#comment-16409333
]
Robert Munteanu commented on OAK-6770:
--------------------------------------
The provisioning model works fine for defining variables, but the problem we're
facing with that is that variables are defined at build time. So imagine we
have a setting like
{noformat}
[variables]
sling.home=sling
[configurations]
org.apache.jackrabbit.foo
location=${sling.home}/foo
org.apache.jackrabbit.bar
location=${sling.home}/bar
{noformat}
The sling.home setting is set in stone to be {{sling}} and I can't change it at
runtime. In contrast, framework properties can be set at runtime so having
{{org.apache.jackrabbit.bar}} inspect the {{sling.home}} framework property is
quite beneficial.
For that reason I'd argue for allowing a fallback to the framework properties
in Oak components.
> Convert oak-segment-tar to OSGi R6 annotations
> ----------------------------------------------
>
> Key: OAK-6770
> URL: https://issues.apache.org/jira/browse/OAK-6770
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
> Reporter: Robert Munteanu
> Assignee: Francesco Mari
> Priority: Minor
> Labels: osgi
> Fix For: 1.10
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
