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 2015/10/21 10:38:27 UTC

[jira] [Resolved] (SLING-5174) Refactor merging of models into separate utility class and add merge options

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

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

Added this utility class with a new merge options class

> Refactor merging of models into separate utility class and add merge options
> ----------------------------------------------------------------------------
>
>                 Key: SLING-5174
>                 URL: https://issues.apache.org/jira/browse/SLING-5174
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Sling Provisioning Model 1.4.0
>
>
> We should move the merge methods from the ModelUtility to a MergeUtility and provide a MergeOptions class which allows to specify:
> - if the  remove run mode should be handled
> - if the latest artifact (default) or the artifact with the highest version wins



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)