[
https://issues.apache.org/jira/browse/MNG-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910322#comment-17910322
]
Tamas Cservenak commented on MNG-8496:
--------------------------------------
Yes, model building changed radically in Maven4, is multi threaded. Also, seems
related MNG-8447, with it at least the output is not overwhelming, as by
default Maven will now tell only "how many" problems it found, and user needs
to use {{-e}} to see them.
> regression: maven 4: same error reported 638 times instead of once
> ------------------------------------------------------------------
>
> Key: MNG-8496
> URL: https://issues.apache.org/jira/browse/MNG-8496
> Project: Maven
> Issue Type: Bug
> Environment: Maven 4.0.0-rc-2, Win11, Java 19
> Reporter: Jörg Hohwiller
> Priority: Major
>
> With maven 3.9.9:
> {code:java}
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> com.customer:myproject-aggregator:${revision}${changelist}
> (D:\projects\myproject\workspaces\main\myproject\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for
> com.customer:myproject.parent:${revision}${changelist}: The following
> artifacts could not be resolved:
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 (absent):
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 was not found
> in https://repo.maven.apache.org/maven2 during a previous attempt. This
> failure was cached in the local repository and resolution is not reattempted
> until the update interval of central has elapsed or updates are forced and
> 'parent.relativePath' points at no local POM @
> com.customer:myproject.parent:${revision}${changelist},
> D:\projects\myproject\workspaces\main\myproject\parent\pom.xml, line 10,
> column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging. {code}
> With Maven 4.0.0-rc-2 I get this error 638 times:
> {code:java}
> [ERROR] The project [inherited]:myproject-parent:pom:[inherited]
> (D:\projects\myproject\workspaces\main\myproject\pom.xml) has 639 errors
> [ERROR] Non-resolvable parent POM: Unable to resolve artifact: The
> following artifacts could not be resolved:
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 (absent):
> Could not find artifact
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 in central
> (https://repo.maven.apache.org/maven2) (remote repositories: central
> (https://repo.maven.apache.org/maven2, default, releases)) and parent could
> not be found in reactor @
> com.customer:myproject.parent:${revision}${changelist},
> file:///D:/projects/myproject/workspaces/main/myproject/parent/pom.xml, line
> 10, column 3
> ...
> [ERROR] Non-resolvable parent POM for
> com.customer:myproject.parent:${revision}${changelist}: Unable to resolve
> artifact: The following artifacts could not be resolved:
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 (absent):
> com.customer.myframework:myframework-dependencies:pom:3.41.0.0 was not found
> in https://repo.maven.apache.org/maven2 during a previous attempt. This
> failure was cached in the local repository and resolution is not reattempted
> until the update interval of central has elapsed or updates are forced
> (remote repositories: central (https://repo.maven.apache.org/maven2, default,
> releases)) and parent could not be found in reactor @
> com.customer:myproject.parent:${revision}${changelist},
> file:///D:/projects/myproject/workspaces/main/myproject/parent/pom.xml, line
> 10, column 3
> ... {code}
> The error between the ... is occurring once in between those 638 occurrences
> of the error listed first. To me it seems as with Maven4 the error is
> reported for every module again or something alike.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
