Hi Guillaume, your proposal is interesting but in the current case it would be confusing, because you would render it as a tree, right? the first two nodes of the tree say: the service is not there, and your bundle needs it.
Well yes, but I can install the bundle and the service is there and it works :-) So maybe the bundle install also needs stronger validation? Fabian On Wed, Feb 11, 2015 at 10:02 PM, Guillaume Nodet <[email protected]> wrote: > On the diagnosis of the error, I'm now quite used to decrypt capabilities / > requirements. I suppose the ResolutionException message could be displayed > in a better way. It currently indicates the path down to the requirement, > it may be easier to understand it the other way around: > - a service of class org.ops4j.pax.url.mvn.MavenResolver can not be found > - which is required by bundle mybundle/1.0.0.SNAPSHOT > - which is required by feature mybundle/1.0.0.SNAPSHOT > I suppose the error display could be improved ...
