[jira] [Commented] (SLING-8128) Consistent ordering of sections when merging features

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696155#comment-16696155 ] 

Carsten Ziegeler commented on SLING-8128:
-----------------------------------------

It seems this problem is due to the fact, that regardless of the order of the statements in the configuration, files are processed first, followed by classifiers, followed by external artifacts.
Now, if you want to use an aggregate as the starting point and then add files, this is currently not possible

> Consistent ordering of sections when merging features
> -----------------------------------------------------
>
>                 Key: SLING-8128
>                 URL: https://issues.apache.org/jira/browse/SLING-8128
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model, Maven Plugins and Archetypes
>            Reporter: Robert Munteanu
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 1.0.0
>
>
> It seems to me that when merging feature files the order in which the content of sections is included is not consistent.
> It seems that, for instance, if I define an aggregate feature the definition order is not respected and the {{repoinit}} section is not ordered correctly.
> This is most visible with repoinit since incorrect ordering leads to failures at runtime, e.g.
> - feature 1 creates /apps
> - features 2 sets ACL on /apps
> If the order is not respected, the startup will fail.



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