You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/06/09 11:11:00 UTC

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

    [ https://issues.apache.org/jira/browse/MRESOLVER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859432#comment-16859432 ] 

Michael Osipov commented on MRESOLVER-43:
-----------------------------------------

Christian, I'd like to merge this. Can you revise the PR and point the Maven change which makes use of this?

> Enhancements to the public API to add support for tracking various informational declaration source hints.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-43
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-43
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: resolver
>            Reporter: Christian Schulte
>            Assignee: Christian Schulte
>            Priority: Minor
>         Attachments: example.log
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)