[
https://issues.apache.org/jira/browse/MRESOLVER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543688#comment-17543688
]
ASF GitHub Bot commented on MRESOLVER-262:
------------------------------------------
cstamas commented on PR #182:
URL: https://github.com/apache/maven-resolver/pull/182#issuecomment-1140492617
> > > How does this change the message usage when this type of information
is collected by default?
> >
> >
> > I don't quite get the question here...
>
> Stupid typo: memory usage
I foresee minimal change, as this does not duplicates any collection, is
really just new "step" instance per collect step. Still, AFAIR @khmarbaise had
some benchmark framework, so would be good to compare on insanely huge projects
I guess....
> 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)
