[
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348672#comment-16348672
]
ASF GitHub Bot commented on FELIX-5782:
---------------------------------------
GitHub user rotty3000 opened a pull request:
https://github.com/apache/felix/pull/131
FELIX-5782 allow resolver errors to be introspected
Signed-off-by: Raymond Augé <rotty3...@apache.org>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rotty3000/felix trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/felix/pull/131.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #131
----
commit 07e9f6ccb6be3c9fa193bcfc1ded607a7622eecd
Author: Raymond Augé <rotty3000@...>
Date: 2018-01-31T20:31:18Z
FELIX-5782 allow resolver errors to be introspected
Signed-off-by: Raymond Augé <rotty3...@apache.org>
----
> allow resolver errors to be introspected
> ----------------------------------------
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
> Issue Type: Improvement
> Components: Resolver
> Reporter: Raymond Augé
> Assignee: Raymond Augé
> Priority: Minor
>
> The current model for resolver errors does not provide any means of
> introspecting deeper knowledge that the resolver gained. The information is
> internal only, which makes user feedback more difficult to produce than
> necessary.
> I propose to expose the error types by means of an exported package
> {{org.apache.felix.resolver.error}}. This will allow interested clients to
> dig more deeply into the reasons for resolution failure in order to provide
> better feedback to users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
