[MRESOLVER-43] Enhancements to the public API to add support for tracking various informational declaration source hints.

**[Christian Schulte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=schulte77)** opened **[MRESOLVER-43](https://issues.apache.org/jira/browse/MRESOLVER-43?redirect=false)** and commented

The Maven Core uses various Maven Resolver API DependencyVisitor implementations to provide debug level messages displaying final resolution results provided by the Maven Resolver. In order to decouple those debug messages from Maven Resolver internal implementation details, the Maven Resolver API needs to be enhanced to provide more information like informational hints to declaration sources. Please see the example log file about how the final debug messages provided by Maven Core could look like. All this information is provided by Maven Resolver without Maven Core having any knowledge about Maven Resolver implementation internals any more.

---

**Attachments:**
- [example.log](https://issues.apache.org/jira/secure/attachment/12912744/example.log) (_6.91 kB_)

Start with the Maven Resolver API and its DependencyVisitor implementations, then review the attached example.log to understand the intended debug output. Identify the API changes needed to expose informational declaration-source hints without Maven Core depending on Resolver internals; completion should provide the information shown by the example log through the public API.

Written by the indexing model from the issue text.