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

ASF GitHub Bot commented on KARAF-5403:
---------------------------------------

GitHub user splatch opened a pull request:

    https://github.com/apache/karaf/pull/380

    KARAF-5403 Fix for loosing order of features given in tooling configuration

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/splatch/karaf KARAF-5403

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/karaf/pull/380.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #380
    
----
commit 51f34067365d72fd853b85ff8b8fd858326871d3
Author: Łukasz Dywicki <[email protected]>
Date:   2017-10-03T12:59:17Z

    KARAF-5403 Fix for loosing order of features given in tooling configuration.

----


> Karaf tooling doesn't keep ordering of features given in configuration
> ----------------------------------------------------------------------
>
>                 Key: KARAF-5403
>                 URL: https://issues.apache.org/jira/browse/KARAF-5403
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>    Affects Versions: 4.0.8
>            Reporter: Łukasz Dywicki
>            Assignee: Łukasz Dywicki
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to