[
https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412355#comment-15412355
]
ASF subversion and git services commented on KARAF-4649:
--------------------------------------------------------
Commit e4c8b2cfdfb2593b0d78a9700c86f36151603264 in karaf's branch
refs/heads/karaf-4.0.x from [~lb]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e4c8b2c ]
[KARAF-4649] In the AssemblyMojo, set blacklistPolicy to null if not defined in
pom
> 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)
