From issues-return-145341-archive-asf-public=cust-asf.ponee.io@maven.apache.org Mon Feb 4 20:46:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D5B19180651 for ; Mon, 4 Feb 2019 21:46:04 +0100 (CET) Received: (qmail 6995 invoked by uid 500); 4 Feb 2019 20:46:03 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 6984 invoked by uid 99); 4 Feb 2019 20:46:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2019 20:46:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 76D43C265E for ; Mon, 4 Feb 2019 20:46:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id mYO0KOSxBoId for ; Mon, 4 Feb 2019 20:46:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 7F5805F543 for ; Mon, 4 Feb 2019 20:46:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id ACBCCE26D7 for ; Mon, 4 Feb 2019 20:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3F6A4243FD for ; Mon, 4 Feb 2019 20:46:00 +0000 (UTC) Date: Mon, 4 Feb 2019 20:46:00 +0000 (UTC) From: "Michael Osipov (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760200#comment-16760200 ] Michael Osipov edited comment on WAGON-541 at 2/4/19 8:45 PM: -------------------------------------------------------------- bq. It seems like the main thrust of your concern was originally that so much of the message was repetitive information. What if you instead simply truncated the output and only showed the first 80 chars of the phrase? Yes, I think that 90% of the users will see the very same information as the status code provided in contrast to {{Requested item is quarantined}}. The problem with 80 chars is that it won't simply scale. Given that almost all standard phrases are less than 80 chars, we'd we back at the beginning of message duplication. Having {{Access denied to: , ReasonPhrase: Forbidden}} does not add any value to the {{Access denied}}. I am thinking of something like {code} my-server false {code} This may work, but I need to evaluate this. I'd be happy if someone could provide a PR for this. was (Author: michael-o): bq. It seems like the main thrust of your concern was originally that so much of the message was repetitive information. What if you instead simply truncated the output and only showed the first 80 chars of the phrase? Yes, I think that 90% of the users will see the very same information as the status code provided in contrast to {{Requested item is quarantined}}. The problem with 80 chars is that it won't simply scale. Given that almost all standard phrases are less than 80 chars, we'd we back at the beginning of message duplication. Having {{Access denied to: , ReasonPhrase: Forbidden}} does not add any value to the {{Access denied}}. I am thinking of something like {code} my-server false {code} This may work, but I need to evaluate this. I'd be happy if someone could provide a PR for this. > 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)