You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2025/01/29 08:18:00 UTC

[jira] [Closed] (MNG-8519) Loss of context/trace in events

     [ https://issues.apache.org/jira/browse/MNG-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet closed MNG-8519.
--------------------------------
    Resolution: Fixed

> Loss of context/trace in events
> -------------------------------
>
>                 Key: MNG-8519
>                 URL: https://issues.apache.org/jira/browse/MNG-8519
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies
>            Reporter: Tamas Cservenak
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.0-rc-3
>
>
> Maven Resolver API elements (like all *Request objects) carry two fields: context and trace. The context explains the "big picture" (ie. project or plugin resolution), while trace gives a "steps" why current call is being executed (ie. resolving a parent POM of some artifact).



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