[ 
https://issues.apache.org/jira/browse/MNG-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912984#comment-17912984
 ] 

Guillaume Nodet commented on MNG-8520:
--------------------------------------

After investigation, [~cstamas] and [~gnodet] found that Maven is missing two 
cache layers:
* missing cache layer around/inside ModelResolver when building projects/models
* missing cache layer when resolving plugins

The first one was present in Maven 3 inside the {{ProjectModelResolver}} and 
should be somehow reimplemented.
The second is not present and has never been, leading to lots of resolutions 
for the same artifacts. This could be plugged in around the calls to the 
resolver inside 
[DefaultPluginDependenciesResolver|https://github.com/apache/maven/blob/13ad6376e00aa5eb28f41a84e0dd06bb1f045c2e/impl/maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java#L232]

> Multiple resolve events for same artifact
> -----------------------------------------
>
>                 Key: MNG-8520
>                 URL: https://issues.apache.org/jira/browse/MNG-8520
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 4.0.0-rc-3
>
>
> Maven Resolver is getting more resolve calls in master than it was getting in 
> Maven 3.x. Example output of user provided issue (see MNG-8518):
> https://gist.github.com/cstamas/83a27c011f19677de1fbbe78712e5357#file-mvn400-txt-L49-L53
> Here, {{org.apache.maven:maven:pom:4.0.0-rc-2}} is resolved 18 times.



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

Reply via email to