[jira] [Comment Edited] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

["Brian Fox (JIRA)" <ji...@apache.org>]

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

Brian Fox edited comment on WAGON-541 at 1/5/19 1:59 AM:
---------------------------------------------------------

We've also experienced this as a regression. When the server chooses to provide additional context, it is not helpful to the user that we squash it. Maven should pass this information on in the error so someone has a chance of understanding what happened. 

 

Here is a more salient example of how this handling regressed:

 
Maven build failures due to firewalled component before Maven 3.6.0 printed a message like 
 
{quote}
Access denied to: <dependency url> , ReasonPhrase:*Requested item is quarantined*
{quote}
 
With Wagon release 3.2.0 ( Maven 3.6.0 ), the reason phrase is no longer printed - it now looks simply like this:
 
{quote}
Access denied to: <dependency url>
{quote}


was (Author: brianf):
We've also experienced this as a regression. When the server chooses to provide additional context, it is not helpful to the user that we squash it. Maven should pass this information on in the error so someone has a chance of understanding what happened. 

> Command Line Not Showing ReasonPhrase for Errors
> ------------------------------------------------
>
>                 Key: WAGON-541
>                 URL: https://issues.apache.org/jira/browse/WAGON-541
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 3.2.0
>         Environment: Windows 10
>            Reporter: Aurelie Pluche
>            Priority: Minor
>         Attachments: MvnCmdLineV339.PNG, MvnCmdLineV339V2.PNG, MvnCmdLineV360.PNG, MvnCmdLineV360V2.PNG
>
>
> Hi,
> I work in the Azure DevOps Artifacts Packaging team at Microsoft where we provide a Maven service to our customers. We often use a Reason-Phrase to return information on failed requests to customers. This functionality was available in previous versions of maven but seems to have disappeared in Maven 3.6.0. Was this intentional?
> I have included screenshots of the cmd line response using two different maven versions (3.3.9 and 3.6.0). I intentionally made a call that would return a 405 error to be able to get an error response. I also used the same package.
> Thanks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)