[
https://issues.apache.org/jira/browse/MNG-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642946#comment-17642946
]
ASF GitHub Bot commented on MNG-7619:
-------------------------------------
laeubi commented on PR #900:
URL: https://github.com/apache/maven/pull/900#issuecomment-1336328111
Not sure if this was already mentioned, but instead of "bake this in" would
it not be better to have a way for (core-)plugins to hook in a
`RepositoryListener` or even on the project level as we already to for
`AbstractMavenLifeCycleListeners` / `WorkspaceReaders`? The this can become
part of m-dependency-p for example.
I also wonder if it is even required to record the data at all, should it
not be sufficient to first load the pom(s), then generate a list of used
plugins and then resolve their dependencies and then do something similar to
`dependency:tree` (maybe plugin-dependency-tree)? To make it more convenient
then one might pass a `-DdependencyReverse=<GAV>` to have a reverse output
rooted at the given GAV when build finished.
> 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)
