You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2015/11/23 18:34:11 UTC
[jira] [Commented] (KARAF-4134) karaf-maven-plugin mixes up
prerequisities
[ https://issues.apache.org/jira/browse/KARAF-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022551#comment-15022551 ]
Andrea Cosentino commented on KARAF-4134:
-----------------------------------------
PR submitted:
https://github.com/apache/karaf/pull/98
> 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)