Am 23.04.2009 17:50 Uhr, schrieb thron7:
>> OK. Answering to myself. I could just use {my.variant} in config.json.
>>
>>
>
> I'm not sure - is it working on your side?! I'd be surprised. This
> "{variantOrSettingsName}" replacement only works for compile output file
> names. I don't think it will be applied to a string value of the "shell"
> key.
Hehe. Nope, I didn't try, but saw these replacements in the config. A
little bit naive ;-)
> Moreover, there is no such thing as the "current variant" for any job
> other than a compile job. So even more doubt about the shell value being
> expanded correctly.
>
> You can use standard config macros in the shell command, like "shell" :
> "echo ${myval}", which should be expanded before running the command.
> But this is fixed at edit-time of the config file(s), and cannot reflect
> a dynamic variants value.
Ah, ok. That might helps in my case. Trying tomorrow...
Thanks,
Cajus
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
