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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

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

Peter lynch commented on WAGON-541:
-----------------------------------

just an update - I have the main code changes in place for adjusted wagon exception messages, with wagon tests. I am currently in the process of manually testing integrations with Maven, wagon-maven-plugin, maven-site-plugin and any other significant wagon project user I can find to make sure that these changes do not make any project regress. After I am satisfied I submit the PR for review

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