[
https://issues.apache.org/jira/browse/SLING-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061440#comment-17061440
]
Carsten Ziegeler commented on SLING-9213:
-----------------------------------------
I've added a now failing test case to
https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/SLING-9213/src/test/java/org/apache/sling/feature/extension/apiregions/APIRegionMergeHandlerTest.java
> Region order is not respected when merging
> ------------------------------------------
>
> Key: SLING-9213
> URL: https://issues.apache.org/jira/browse/SLING-9213
> Project: Sling
> Issue Type: Bug
> Components: Feature Flags
> Affects Versions: Feature Model API Regions Extension 1.1.4
> Reporter: Carsten Ziegeler
> Priority: Blocker
> Fix For: Feature Model API Regions Extension 1.1.6
>
>
> The regions of the source are always put in front of the regions of the
> target. If the source is using less regions than the target, this might
> change the ordering of regions.
> Example: source has a single region M, target has three regions T,M,B - after
> merging the result should still be T, M, B. But right now it is M, T, B
> This breaks then the second feature - and potentially other features merged
> in afterwards.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
