You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/08/08 19:59:20 UTC

[jira] [Resolved] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom

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

Jean-Baptiste Onofré resolved KARAF-4649.
-----------------------------------------
    Resolution: Fixed

> AssemblyMojo : blacklistPolicy set to null if not defined in pom
> ----------------------------------------------------------------
>
>                 Key: KARAF-4649
>                 URL: https://issues.apache.org/jira/browse/KARAF-4649
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>            Reporter: Luca Burgazzoli
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.1.0, 4.0.6
>
>
> In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo sets the policy the assembly Builder should use, it is not explicit configured in the pom, it sets it to null overriding the default value defined by Builder.
> The effect is that if you do not set the policy in pom, the blacklisted bundles are still listed i.e. in startup.properties.



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