[
https://issues.apache.org/jira/browse/MRESOLVER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552234#comment-17552234
]
ASF GitHub Bot commented on MRESOLVER-262:
------------------------------------------
cstamas commented on PR #182:
URL: https://github.com/apache/maven-resolver/pull/182#issuecomment-1151164419
> darn, I always lag behind... What kind of transport? ;)
Sorry, spoke too early: I just spotted you play with 3.8.6 while this is in
3.9.0 and above only https://issues.apache.org/jira/browse/MNG-7454
(you can use it with 3.8.6 as well, but is a bit more complicated, just
follow steps as here https://github.com/apache/maven/pull/635)
> Provide contextual data in trace data for collector invoked requests
> --------------------------------------------------------------------
>
> Key: MRESOLVER-262
> URL: https://issues.apache.org/jira/browse/MRESOLVER-262
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamás Cservenák
> Priority: Major
> Fix For: 1.8.1
>
>
> During collection several RepositoryEvents are fired, but they does not carry
> any context related data regarding artifact collection.
> Simplest solution would be to extend RequestTrace to provide:
> * request context
> * the artifact path (from root to leaf)
> * leaf artifact being collected
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
