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

ASF GitHub Bot commented on MRESOLVER-262:
------------------------------------------

grgrzybek commented on PR #182:
URL: https://github.com/apache/maven-resolver/pull/182#issuecomment-1150864268

   Dependencies can be tracked as expected. It works different for child→parent 
relationship, because the path is not passed down with `RequestTrace`.
   
   Most of the projects being built on fresh repo starts with:
   ```
   Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
   Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
 (3.9 kB at 8.9 kB/s)
   Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/22/maven-plugins-22.pom
   Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/22/maven-plugins-22.pom
 (13 kB at 157 kB/s)
   Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/21/maven-parent-21.pom
   Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/21/maven-parent-21.pom
 (26 kB at 277 kB/s)
   Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/apache/10/apache-10.pom
   Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/apache/10/apache-10.pom (15 kB 
at 197 kB/s)
   Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.jar
   Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.jar
 (25 kB at 254 kB/s)
   ```
   
   However for org.apache:apache:pom:10, I could track this information (in 
fresh M2 repo in 
`org/apache/apache/10/.tracking/org.apache.maven.plugins_maven-clean-plugin_2.5.plugin`
 file):
   ```
   org.apache:apache:pom:10
     org.apache.maven.plugins:maven-clean-plugin:2.5
       org.apache.maven:maven-core:3.8.6.1:default-lifecycle-bindings (implicit)
   
   Repository: central (https://repo.maven.apache.org/maven2, default, releases)
   ```
   
   It'd be great to insert these:
   * org/apache/maven/plugins/maven-plugins/22
   * org/apache/maven/maven-parent/21
   
   but for now let's leave as is - parent-child relationship is much less 
relevant than normal dependencies.
   
   What's most important is 
`log4j/log4j/1.2.12/.tracking/org.apache.maven.plugins_maven-compiler-plugin_jar_3.1.dep`
 file with:
   ```
   log4j:log4j:jar:1.2.12 (compile) (plugin)
     org.apache.xbean:xbean-reflect:jar:3.4 (compile) (plugin)
       org.codehaus.plexus:plexus-container-default:jar:1.5.5 (compile) (plugin)
         org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 () (plugin)
   
   Repository: central (https://repo.maven.apache.org/maven2, default, releases)
   ```




> 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)

Reply via email to