[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863452#comment-17863452
]
Guillaume Nodet commented on MNG-7771:
--------------------------------------
I don't see any place in Maven where this exception is created. AFAIK, it
always comes from the resolver.
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
> Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
> Reporter: Michael Osipov
> Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
