You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2014/04/24 17:52:15 UTC

[jira] [Resolved] (FELIX-4492) Enhance resolver logging to get better uses diagnostics

     [ https://issues.apache.org/jira/browse/FELIX-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall resolved FELIX-4492.
------------------------------------

    Resolution: Fixed
      Assignee: Richard S. Hall

Patch applied. Please close.

> Enhance resolver logging to get better uses diagnostics
> -------------------------------------------------------
>
>                 Key: FELIX-4492
>                 URL: https://issues.apache.org/jira/browse/FELIX-4492
>             Project: Felix
>          Issue Type: Improvement
>          Components: Resolver
>    Affects Versions: resolver-1.0.0
>            Reporter: Thomas Watson
>            Assignee: Richard S. Hall
>             Fix For: resolver-1.2.0
>
>         Attachments: org.apache.felix.resolver.patch
>
>
> There is lots of useful information the resolver encounters while trying to resolve a consistent class space having to do with uses constraint violations.  The felix resolver encodes a nice chain message contained in a ResolutionException that can help diagnose uses constraint issues.
> It would be helpful if the Logger was enhanced to be able to capture the ResolutionException for uses constraint violations as they occur during the resolve process.



--
This message was sent by Atlassian JIRA
(v6.2#6252)