[
https://issues.apache.org/jira/browse/MNG-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940802#comment-17940802
]
Guillaume Nodet edited comment on MNG-8671 at 4/3/25 7:03 PM:
--------------------------------------------------------------
Yes, I don't think we want to break all Maven 3 plugins, so targeting the new
API would definitely make sense.
I think this can easily be done by:
* making {{RequestTrace}} non nullable on {{Request}}
* making {{context}} non nullable on {{RequestTrace}}
was (Author: gnt):
Yes, I don't think we want to break all Maven 3 plugins, so targeting the new
API would definitely make sense.
> Resolver context usage should be enforced
> -----------------------------------------
>
> Key: MNG-8671
> URL: https://issues.apache.org/jira/browse/MNG-8671
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> This one is tricky, as it tackles Maven Core but also Maven Plugins,
> basically {_}everything that is using Resolver API{_}.
> All the Resolver request objects (most) carries "context" string, that is
> unused in Resolver itself, but carries possible extra information to those
> listening in, like "in which context is this resolver request executing".
> Maven4 also offers similar API, maybe we want to target this issue for Maven
> 4 only, as again, properly fixing this in Maven 3 is nearly impossible, would
> tackle all code touching resolver APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
