[
https://issues.apache.org/jira/browse/MNG-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923734#comment-17923734
]
Alexis Tual commented on MNG-8518:
----------------------------------
After some investigation, it turns out those issues are due to the trace object
now being a `org.apache.maven.api.model.Plugin`, whereas it was a
`org.apache.maven.model.Plugin` in Maven 3. If you confirm that is expected, we
will adapt our code.
> 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)
