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

Michael Osipov commented on MNG-7771:
-------------------------------------

Correct, [~cstamas] nailed it mostly. The information has to be in the 
exception and Maven has to expose it correct. Neither is. Even if the issue is 
not in Maven per sé, the issue is visible from Maven from a user's PoV.

> 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)

Reply via email to