You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2022/12/03 21:23:00 UTC
[jira] [Updated] (MNG-7619) Maven should explain why an artifact is present in local repository
[ https://issues.apache.org/jira/browse/MNG-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MNG-7619:
---------------------------------
Description:
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.
> 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)