[ https://issues.apache.org/jira/browse/FELIX-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-2841. ---------------------------------- Resolution: Fixed Committed a fix for this, now the error message trying to print a formatted dependency graph to show you where the constraint violation occurs, such as: DEBUG: Candidate permutation failed due to a conflict between imports; will try another if possible. (org.apache.felix.framework.resolver.ResolveException: Unable to resolve module A [6.0] because it is exposed to package 'bar' from B [1.0] and D [3.0] via two dependency chains. Chain 1: A [6.0] import: (&(package=bar)(version>=1.0.0)(!(version>=2.0.0))) | export: package=bar B [1.0] Chain 2: A [6.0] import: (&(package=woz)(version>=1.0.0)(!(version>=2.0.0))) | export: package=woz; uses:=boz C [2.0] import: (&(package=boz)(version>=1.0.0)(!(version>=2.0.0))) | export: package=boz; uses:=bar export: package=bar D [3.0]) > [Framework] Improve resolve exception messages > ---------------------------------------------- > > Key: FELIX-2841 > URL: https://issues.apache.org/jira/browse/FELIX-2841 > Project: Felix > Issue Type: Improvement > Components: Framework > Affects Versions: framework-3.0.8 > Reporter: Richard S. Hall > Assignee: Richard S. Hall > Priority: Minor > Fix For: framework-3.2.0 > > > The resolve exception messages currently print useful information, but do so > in a way that is difficult to understand. We should try to re-word/re-format > the messages to make them more meaningful to the average person. For example, > see the discussion here: > http://www.osgi.org/blog/2011/01/error-messages.html > Additionally, we log the exceptions multiple times, so we should try to avoid > that as much as possible. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira