HI all,

I also thought that recursively replacing variables was supported, but I
tried it this morning quickly and apparently it's not.

Maybe create a JIRA for it?

Best regards,

David

On Mon, 24 Aug 2020 at 12:00, Carsten Ziegeler <[email protected]> wrote:

> Hi Robert,
>
> ok, thanks for clarifying. Yes, I agree it makes sense to support a) as
> well - and actually I'm a little bit surprised that it is not :)
> I guess the only change needed is to recursively process replacements of
> variables which should be an easy fix
>
> Regards
> Carsten
>
> Am 24.08.2020 um 12:55 schrieb Robert Munteanu:
> > Hi Carsten,
> >
> > On Sat, 2020-08-22 at 14:27 +0200, Carsten Ziegeler wrote:
> >> 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?
> >
> > I wanted to achieve both scenarios:
> >
> > a) if no variable is passed from the CLI, persistence.dir should point
> > to the resovled value of "sling.home" and "/persistence"
> > b) if the variable value is overridden, the override should be used
> >
> > b) works today, but a) does not. I tried to give my problem a bit more
> > context with an exampe, but I guess I ended up creating confusion :-)
> >
> > So basically I would like "${sling.home}/repository" to be properly
> > resolved for variables like it is done for configurations for instance.
> >
> > Thanks,
> > Robert
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> [email protected]
>

Reply via email to