karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4134) karaf-maven-plugin mixes up prerequisities
Date Mon, 23 Nov 2015 17:37:10 GMT

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

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

GitHub user oscerd opened a pull request:

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

    [KARAF-4134] karaf-maven-plugin mixes up prerequisities

    Hi all,
    
    This PR is related to:
    https://issues.apache.org/jira/browse/KARAF-4134
    
    Andrea

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

    $ git pull https://github.com/oscerd/karaf KARAF-4134

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

    https://github.com/apache/karaf/pull/99.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 #99
    
----
commit bb7b80350055e35b92c01f703e81857da81a6ae5
Author: Andrea Cosentino <ancosen@gmail.com>
Date:   2015-11-23T16:50:53Z

    [KARAF-4134] karaf-maven-plugin mixes up prerequisities

----


> karaf-maven-plugin mixes up prerequisities
> ------------------------------------------
>
>                 Key: KARAF-4134
>                 URL: https://issues.apache.org/jira/browse/KARAF-4134
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-profile
>    Affects Versions: 4.0.3
>            Reporter: Toni Fadjukoff
>            Priority: Minor
>
> When karaf-assembly packaging is used with such a configuration that multiple prerequisities
gets pulled, the ordering will be mixed up.
> Problem is that profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java
sorts the parts incorrectly using TreeSet in reformatClauses().
> For example, if first this was generated from plugin configuraion (aries-blueprint, deployer,
wrap), camel-core, camel-blueprint, it will be after reformatClauses (aries-blueprint, camel-core,
camel-blueprint, deployer, wrap)
> Note: the example is not complete as wrap and blueprint dependencies will only be pulled
if such bundles are used too.
> Relevant issues where this was first implemented are KARAF-2988 and KARAF-3574.



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

Mime
View raw message