You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2019/06/18 06:09:00 UTC

[jira] [Resolved] (SLING-8520) Improve artifact/bundle merging

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

Carsten Ziegeler resolved SLING-8520.
-------------------------------------
    Resolution: Fixed

I've adjusted the merging process as described in rev b67c8bb
In addition I changed the type of an override rule from String to ArtifactId - as an override rule  is exactly that. This makes handling of the rules easier and avoids parsing them over and over again.
We could potentially further improve the algorithm as there is some stuff done several times during merging, but I'll leave that to another issue

> Improve artifact/bundle merging
> -------------------------------
>
>                 Key: SLING-8520
>                 URL: https://issues.apache.org/jira/browse/SLING-8520
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model 1.0.6
>
>
> Currently when there is a clash during merging of two features, the selected bundle/artifact is always appended at the end, even if it is the same as already in the list of artifacts (target). However, to keep the original order the selected bundle/artifact should be placed at the same position as the bundle/artifact in the target.
> Further more the code currently does not completely handle classifiers correctly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)