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 2020/10/08 13:49:00 UTC
[jira] [Assigned] (KARAF-6605) Introduce feature configuration to
ignore effective capability in the resolver
[ https://issues.apache.org/jira/browse/KARAF-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-6605:
-------------------------------------------
Assignee: (was: Jean-Baptiste Onofré)
> Introduce feature configuration to ignore effective capability in the resolver
> ------------------------------------------------------------------------------
>
> Key: KARAF-6605
> URL: https://issues.apache.org/jira/browse/KARAF-6605
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
> Reporter: Jean-Baptiste Onofré
> Priority: Major
>
> The specification says:
> The OSGi framework resolver only considers Capabilities without an effective directive or effective:=resolve. Capabilities with other values for the effective directive can be considered by an external agent.
> The effectiveness active is a convention commonly used for situations that do not need to be resolved by the OSGi framework but are relevant in using the resolver for assembling applications.
> The feature resolver considers the capability as a strong requirement, whatever if it's effective or not.
> I think it makes sense to consider this capability requirement for the build, but runtime could consider effective capability as optional.
> It would be great to either update the features resolver that way or add a configuration in org.apache.karaf.features.cfg defining strong or optional requirement for effective cap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)