[
https://issues.apache.org/jira/browse/MNG-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642964#comment-17642964
]
ASF GitHub Bot commented on MNG-7619:
-------------------------------------
cstamas commented on PR #900:
URL: https://github.com/apache/maven/pull/900#issuecomment-1336366201
@laeubi while I agree with ideas you wrote, I am still for this PR to go in,
here is why:
This PR is (nearly) trivial, but gives you powerful tool (for investigation,
answering several questions), is registered early (earliest possible), and does
not prevent anything of those you wrote (a plugin). Moreover, by being earliest
present, and present during whole session of a real build, it covers
_everything_ (even some plugin that may dynamically resolve). Not easily done
with something like build extension or even plugin (they are all too late to
cover everything).
Also, none of these prevents anything of those things you wrote, this is
totally orthogonal. I personally see this like `-X`, a handy switch seldom used
by users, but when one needs it, is very very handy.
> Maven should explain why an artifact is present in local repository
> -------------------------------------------------------------------
>
> Key: MNG-7619
> URL: https://issues.apache.org/jira/browse/MNG-7619
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.0, 4.0.x-candidate, 4.0.0-alpha-3
>
>
> Ability to make Maven record:
> * why given artifact is present in local repository
> * record reverse dep tree how this artifact got resolved
> This is mostly for detecting dependency resolution anomalies, ideally best
> combined with {{-Dmaven.repo.local}} when you use new/empty local repo to
> build a project. After the build, you will end up with reverse dep trees in
> {{.tracking}} directories for each artifact.
> To enable, pass {{-Dmaven.repo.local.recordReverseTree}} on CLI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
