[MNG-6584] Maven version 3.6.0 does not show ReasonPhrase anymore

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0
• Fix Version/s: 3.6.3
• Assignee: Herve Boutemy
• Reporter: Lucas Ludueño
• Created: 31/Jan/19 21:15
• Updated: 22/Dec/21 21:31
• Resolved: 13/Nov/19 06:30

Description

Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for example when you run mvn deploy to a custom Maven service).

With version 3.5.0 the ReasonPhrase is shown in a message like:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project mule-module-tooling-service: Failed to deploy artifacts: Could not transfer artifact 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 from/to exchange-repository (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to transfer file: http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1]

I am not completely sure if the ReasonPhrase has been removed intentionally. If the answer is no, can you fix it? If the answer is yes, how can I simulate the behavior to indicate to someone what was happening?

 

Thanks!!

 

Issue Links

• depends upon: WAGON-541 Command Line Not Showing ReasonPhrase for Errors
• is caused by: WAGON-529 Clean up inconsistent status code and reason phrase handling
• relates to: MNG-6795 define a replacement for ReasonPhrase to display details about transfert failures