[
https://issues.apache.org/jira/browse/MNG-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923740#comment-17923740
]
Guillaume Nodet commented on MNG-8518:
--------------------------------------
Yes, this is an expected change when running in Maven 4. The core is being
switched to the new Maven API and internal objects will be moved to the new
model. This is a clear example. The problem is that the object is untyped, so
there's not much we can do here...
> Unexpected dependency resolution events with Maven 4
> ----------------------------------------------------
>
> Key: MNG-8518
> URL: https://issues.apache.org/jira/browse/MNG-8518
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 4.0.0-rc-2
> Reporter: Alexis Tual
> Priority: Major
> Fix For: 4.0.0-rc-3
>
>
> An extension listening to {{RepositoryEvent}} will show significantly more
> dependency resolution requests with Maven 4.x than with Maven 3.x.
> I've included a reproduction with more details:
> [https://github.com/alextu/maven4-deps-reproducer].
> Our regression suite for Maven 4.x started to fail on December 13, 2024, so
> something caused this behavior before this date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
