[
https://issues.apache.org/jira/browse/MNG-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280683#comment-17280683
]
Michael Osipov commented on MNG-6795:
-------------------------------------
[~tcrawley], headers denote metadata, not messages. Using a header seems wrong
to me. I was thinking about using RFC 7807, but frankly Wagon cannot and will
not make any assumptions about the target endpoint. So, without knowing the
actual context Wagon is running in it is virtually impossible to do so. Also
note that Wagon is generic transport, not related to Maven repositories at all.
Another problem is that Wagon is protocol agnostic, this means that even if we
add those information to Wagon exceptions, it remains unused for ther Wagon
implementations except HTTP.
WDYT?
> define a replacement for ReasonPhrase to display details about transfert
> failures
> ---------------------------------------------------------------------------------
>
> Key: MNG-6795
> URL: https://issues.apache.org/jira/browse/MNG-6795
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories
> Affects Versions: 3.3.9, 3.6.3
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> as documented in WAGON-541
> [372aa52c80c2f7b458c095d837e15ebeafbdf0b7|https://gitbox.apache.org/repos/asf?p=maven-wagon.git&a=commit&h=372aa52c80c2f7b458c095d837e15ebeafbdf0b7],
> ReasonPhrase has been removed from HTTP/2 and deprecated (optional) in
> HTTP/1.1 for more than five years. It is useful to give detailed error
> messages on artifact transfert errors with a repository manager.
> A replacement has to be found
--
This message was sent by Atlassian Jira
(v8.3.4#803005)