You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2019/10/27 17:05:00 UTC

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

     [ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated WAGON-541:
--------------------------------
    Fix Version/s: 3.3.4

> 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
>             Fix For: 3.3.4
>
>         Attachments: MvnCmdLineV339.PNG, MvnCmdLineV339V2.PNG, MvnCmdLineV360.PNG, MvnCmdLineV360V2.PNG
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)