Robert Munteanu wrote
> Hi,
>
> On Wed, 2016-12-14 at 12:57 +0100, Carsten Ziegeler wrote:
>> Hi,
>>
>> I think what should work is to use variables/properties defined in
>> the pom:
>> In the prov model you have
>> [variables]
>> mpx.repository=${foo}
>>
>> in the pom you have
>> <properties>
>> <foo>${sling.home}/repository</foo>
>> </properties>
>>
>> and then you set <usePomVariables>true</usePomVariables> for the
>> slingstart maven plugin configuration.
>>
>> And finally you can use the maven mechanisms to override the property
>> value for foo.
>
> Thanks for the reply. What that means though is that I can't use that
> at runtime, when running the slingstart, right?
True
Carsten
>
> But on the other hand I should be able to drop in a config file and
> that would override the property, which should be fine.
>
> Thanks,
>
> Robert
>
>>
>> Regards
>> Carsten
>>
>> Robert Munteanu wrote
>>> Hi,
>>>
>>> I'm trying to set a 'dynamic' property in the slingstart model,
>>> based
>>> on sling.home:
>>>
>>> [variables]
>>> mpx.repository.home=${sling.home}/repository
>>>
>>> The idea is to allow the user to redefine it at runtime via system
>>> properties:
>>>
>>> java -jar ... -Dmpx.repository.home=/some/place
>>>
>>> Is this possible using slingstart? If not, what solutions do I have
>>> to
>>> enable this kind of usage?
>>>
>>> Thanks,
>>>
>>> Robert
>>>
>>
>>
>>
>>
>
>
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
