Community
Participate
Working Groups
Created attachment 133829 [details] Screenshot example The target tracks errors separately based on whether they are resolution errors (directory foo does not exist) or bundle errors (bundle bar has a bad manifest). Different errors can be returned depending on which API is used. Sometimes we separated the two types of errors by checking whether the status was a multi-status. It was expected that a resolution that failed would return a single status. The p2 target provisioner will sometimes return a multi-status (see screenshot for an example). So far the only UI problem I see happening is that turning on "Show plug-in content" ends up hiding the resolution errors. There may be other problems and we should try to polish the API.
I will try to add a bit of polish to this for 3.6 since the new api isn't going in.
Fixed in HEAD. See TargetLocationGroup. Multistatuses will now have their trees visible in the location group. If the user turns on show plug-in content, the errors will still disappear. The only way to fix that trivial problem would involve changing the API.
