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

ASF GitHub Bot commented on MNG-7741:
-------------------------------------

grgrzybek opened a new pull request, #1058:
URL: https://github.com/apache/maven/pull/1058

   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed
          for the change (usually before you start working on it).  Trivial 
changes like typos do not
          require a JIRA issue. Your pull request should address just this 
issue, without
          pulling in other changes.
    - [ ] Each commit in the pull request should have a meaningful subject line 
and body.
    - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,
          where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA 
issue.
    - [ ] Also format the first line of the commit message like `[MNG-XXX] 
SUMMARY`.
          Best practice is to use the JIRA issue title in both the pull request 
title and in the first line of the commit message.
    - [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will
          be performed on your pull request automatically.
    - [ ] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [ ] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> Add more information when using -Dmaven.repo.local.recordReverseTree=true
> -------------------------------------------------------------------------
>
>                 Key: MNG-7741
>                 URL: https://issues.apache.org/jira/browse/MNG-7741
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Grzegorz Grzybek
>            Priority: Major
>
> I much appreciate adding {{-Dmaven.repo.local.recordReverseTree=true}} option 
> to Maven Core (supported by new resolver features).
> After initial idea, I added few more options to 
> https://github.com/grgrzybek/tracking-maven-extension and I'd be happy to see 
> these in {{org.apache.maven.internal.aether.ReverseTreeRepositoryListener}}.
> I did some experiments locally and I have improvement ready which:
> h5. tracks information about missing dependencies
> when using non-existing dependency (like {{org.slf4j:slf4j-apix}}), I can see 
> {{~/.m2/repository/org/slf4j/slf4j-apix/1.7.36/.tracking/grgr_simplest_jar_1.0.miss}}
>  file with:
> {noformat}
> org.slf4j:slf4j-apix:pom:1.7.36
>   org.slf4j:slf4j-apix:jar:1.7.36 (compile) (project)
>     grgr:simplest:jar:1.0 (project)
> Configured repositories:
>  - central : https://repo.maven.apache.org/maven2
> {noformat}
> h5. tracks information about actual repository information (in 
> {{_remote.repositories}} we have only the ID)
> For example
> {noformat}
> org.apache.maven.plugins:maven-compiler-plugin:pom:3.10.1
>   org.apache.maven.plugins:maven-compiler-plugin:3.10.1
>     org.apache.maven:maven-core:3.9.1:default-lifecycle-bindings (implicit)
> Repository: central (https://repo.maven.apache.org/maven2, default, releases)
> {noformat}
> h5. tracks information where only POM is downloaded
> For example with 
> {{~/.m2/repository/com/google/guava/guava-parent/16.0.1/.tracking/org.apache.maven.plugins_maven-surefire-plugin_jar_3.0.0.dep}}:
> {noformat}
> com.google.guava:guava-parent:pom:16.0.1
>   com.google.guava:guava:jar:16.0.1 (compile) (plugin)
>     org.sonatype.sisu:sisu-guice:jar:no_aop:3.2.3 (compile) (plugin)
>       org.apache.maven:maven-core:jar:3.2.5 (provided) (plugin)
>         org.apache.maven.shared:maven-common-artifact-filters:jar:3.1.1 
> (compile) (plugin)
>           org.apache.maven.surefire:maven-surefire-common:jar:3.0.0 (compile) 
> (plugin)
>             org.apache.maven.plugins:maven-surefire-plugin:jar:3.0.0 () 
> (plugin)
> Repository: central (https://repo.maven.apache.org/maven2, default, releases)
> {noformat}
> h5. tracks reverse trees originating from plugins (also implicit ones)
> {noformat}
> org.apache:apache:pom:26
>   org.apache.maven.plugins:maven-resources-plugin:3.3.0
>     org.apache.maven:maven-core:3.9.1:default-lifecycle-bindings (implicit)
> Repository: central (https://repo.maven.apache.org/maven2, default, releases)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to