[
https://issues.apache.org/jira/browse/FELIX-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739656#comment-16739656
]
David Jencks commented on FELIX-6019:
-------------------------------------
I'm getting more confused. Reading the comments to KARAF-3520 my impression is
that there is universal agreement that karaf's 2015 behavior of failing to
deploy a feature due to unmatched service requirements marked effective:=active
is wrong and that this behavior was changed. However, there's no linked commit
so perhaps nothing actually happened?
If there is a possible interpretation of this karaf issue that supports
mandatory service requirement-capability matching please explain.
The discussion there also suggests an additional workaround, namely adding a
bogus capability that will satisfy service matching to the karat feature
description.
> Provide a bnd plugin to remove header parameters
> ------------------------------------------------
>
> Key: FELIX-6019
> URL: https://issues.apache.org/jira/browse/FELIX-6019
> Project: Felix
> Issue Type: New Feature
> Reporter: Oliver Lietz
> Assignee: Oliver Lietz
> Priority: Major
>
> The plugin removes parameters from bundle headers.
> See bnd issue [#2429|https://github.com/bndtools/bnd/issues/2429] and
> SLING-8178.
> Example instruction (for bnd file):
> {noformat}
> -plugin:\
> org.apache.felix.bnd.plugins.header.RemoveParametersPlugin;\
>
> 'Require-Capability'='osgi.service;filter:="(objectClass=org.osgi.service.event.EventAdmin)";effective:=active,osgi.service;filter:="(objectClass=org.osgi.service.event.EventHandler)";effective:=active;cardinality:=multiple'
> {noformat}
> Initial source:
> https://svn.apache.org/repos/asf/felix/sandbox/olli/org.apache.felix.bnd.plugins/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
