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 2015/08/12 06:35:46 UTC
[jira] [Updated] (KARAF-3725) Improve diagnosing of unresolved
optional requirements
[ https://issues.apache.org/jira/browse/KARAF-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-3725:
----------------------------------------
Fix Version/s: (was: 4.0.1)
> Improve diagnosing of unresolved optional requirements
> ------------------------------------------------------
>
> Key: KARAF-3725
> URL: https://issues.apache.org/jira/browse/KARAF-3725
> Project: Karaf
> Issue Type: Improvement
> Reporter: Guillaume Nodet
>
> KARAF-3722 is a good example of the problem.
> Diagnosing that the optional requirement is not resolved is the first problem, then understanding why is another big problem.
> We need a way to inform the user when / why optional requirements are not resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)