You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2023/06/01 13:09:00 UTC
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[ https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728356#comment-17728356 ]
Guillaume Nodet commented on MNG-7771:
--------------------------------------
AFAIK, {{ArtifactResolutionException}} are thrown from old services in maven-compat, so I don't think we should waste any time on those.
> 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.8.x-candidate, 3.9.x-candidate, 4.0.x-candidate
>
>
> {{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)