Ok, that’s fine. I will change the PM to FM Converter so that variables inside
the bundles are replaced with the actual value.
- Andy
> On May 23, 2019, at 11:11 PM, Karl Pauls wrote:
>
> That said, maven properties can be used - hence, if you want to just have
> the version in one place in yo
That said, maven properties can be used - hence, if you want to just have
the version in one place in your build you can by using a maven property.
The difference is build time vs deploy/runtime.
regards,
Karl
On Friday, May 24, 2019, Carsten Ziegeler wrote:
> Hi,
>
> variables are not suppor
Hi,
variables are not supported for bundle ids by design. Reasoning behind
this is in the end reproducibility. A specific feature should be the
same everywhere. With variables in the ids it would be possible that
different artifacts are used in different situations for the same feature.
Now,
Hi
According to the FeatureBuilder:
/**
* Resolve variables in the feature.
* Variables are allowed in the values of framework properties and in the
values of
* configuration properties.
* @param feature The feature
* @param additionalVariables Optional additional variables
*/
public stati
