Currently, when there are exceptions while resolving an artifact or a library, those exceptions are logged and then discarded. If, e.g., obtaining PomInformation for an artifact is not possible, it will simply not have any information annotated, but will otherwise be passed to client analyses normally. Now that we have ResolutionContext objects that are maintained throughout the entire resolution process of one particular artifact or library, it would make sense to aggregate exceptions - maybe together with the specific indentifier for which the exception occurred - in the respective resolution context, and provide it to clients.
Currently, when there are exceptions while resolving an artifact or a library, those exceptions are logged and then discarded. If, e.g., obtaining
PomInformationfor an artifact is not possible, it will simply not have any information annotated, but will otherwise be passed to client analyses normally. Now that we haveResolutionContextobjects that are maintained throughout the entire resolution process of one particular artifact or library, it would make sense to aggregate exceptions - maybe together with the specific indentifier for which the exception occurred - in the respective resolution context, and provide it to clients.