You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2019/08/20 16:06:00 UTC

[jira] [Resolved] (SLING-8644) Improve Startorder handling during merge

     [ https://issues.apache.org/jira/browse/SLING-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved SLING-8644.
-------------------------------
    Resolution: Fixed

> Improve Startorder handling during merge
> ----------------------------------------
>
>                 Key: SLING-8644
>                 URL: https://issues.apache.org/jira/browse/SLING-8644
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model 1.0.6
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Feature Model 1.1.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When merging features we should pick the lowest startorder for clashing artifacts to make it predictable what order is going to be picked. Furthermore, we have make it so that prototype is merging with ALL to make the startorder selection work and while we are add it, fix the ALL merge that is currently broken when there are more then one version in both features. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)