Hi,
I guess it depends on how this support should look like. I would assume,
that "-V persistence.dir=/data" with your example works and uses "/data"
for the persistence. It will not use "${sling.home}/data" - not sure if
that was your intention?
Regards
Carsten
Am 20.08.2020 um 23:03 schrieb Robert Munteanu:
Hi,
I noticed that variables are declared to be supported as part of
configurations and framework properties. In addition to that, I think
it would be very useful to replace them in variable values as well. It
would go well with providing reasonable defaults which can then be
overriden from the command line.
As an example, the following feature file:
{
"variables": {
"persistence.dir": "${sling.home}/persistence"
},
"configurations": {
"com.foo.Persister": {
"data": "${persistence.dir}"
}
}
}
will by default store data under launcher/persistence. However, I will
be able to redirect it anywhere with
-V persistence.dir=/data
Right now this isn't possible. Is this something that could be done
with the feature model?
Thanks,
Robert
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
