+1
> On 14 Aug 2019, at 08:39, Konrad Windszus wrote:
>
> I would actually refuse to merge if the same PID occurs. It might be
> unexpected (and incompatible) if you do transparent merging on the property
> level.
> It is just important that it is easy to resolve those conflict without
> touc
On Wednesday, August 14, 2019, Konrad Windszus wrote:
> Hi,
> I would actually refuse to merge if the same PID occurs. It might be
> unexpected (and incompatible) if you do transparent merging on the property
> level.
> It is just important that it is easy to resolve those conflict without
> touc
Hi,
I would actually refuse to merge if the same PID occurs. It might be unexpected
(and incompatible) if you do transparent merging on the property level.
It is just important that it is easy to resolve those conflict without touching
the feature, i.e. some force option which enforces merging (w
Hi,
when two features are merged (aggregated), configurations are
automatically merged. Meaning if both features have a configuration for
the same PID, the properties from the second feature are put into the
configuration of the first feature, adding and potentially overwriting
values.
Howe
