[jira] [Comment Edited] (FELIX-5782) allow resolver errors to be introspected

["Raymond Augé (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374825#comment-16374825 ] 

Raymond Augé edited comment on FELIX-5782 at 2/23/18 6:46 PM:
--------------------------------------------------------------

I could take that approach if you prefer.

How about:
{code:java}
class abstract ResolutionFailureException extends ResolutionException {
     public enum Reason { DynamicImport, FragmentNotSelected, MissingRequirement, UseConstraint }

     public abstract Reason getReason();
}
{code}


was (Author: rotty3000):
I could take that approach if you prefer.

How about:

{code}
class abstract ResolutionFailureException extends ResolutionException {
     public enum Reason \{ DynamicImport, FragmentNotSelected, MissingRequirement, UseConstraint }

     public abstract Reason getReason();
}
{code}

> 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: Thomas Watson
>            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)