You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/12/03 10:41:00 UTC
[jira] [Moved] (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 ]
Michael Osipov moved MNG-6534 to WAGON-541:
-------------------------------------------
Affects Version/s: (was: 3.6.0)
3.2.0
Component/s: (was: Command Line)
wagon-http
Key: WAGON-541 (was: MNG-6534)
Project: Maven Wagon (was: Maven)
> 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, MvnCmdLineV360.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)