Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2920B11294 for ; Fri, 2 May 2014 17:11:18 +0000 (UTC) Received: (qmail 39353 invoked by uid 500); 2 May 2014 17:11:15 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 39222 invoked by uid 500); 2 May 2014 17:11:15 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 39212 invoked by uid 99); 2 May 2014 17:11:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2014 17:11:15 +0000 Date: Fri, 2 May 2014 17:11:15 +0000 (UTC) From: "Benedikt Ritter (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (LANG-1004) DurationFormatUtils#formatDurationHMS implementation does not correspond to Javadoc and vice versa 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/LANG-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987919#comment-13987919 ] Benedikt Ritter edited comment on LANG-1004 at 5/2/14 5:10 PM: --------------------------------------------------------------- Hi Michael, nice patch! However I'm a bit afraid this change will break clients that are using the method as it is now. What do you think? The main use case is probably formatting for displaying a value (in the GUI or in some kind of log file). So it may not be a problem? Benedikt EDIT: how about providing a new method called {{formatDurationISOHMS}} which formats the way you propose? was (Author: britter): Hi Michael, nice patch! However I'm a bit afraid this change will break clients that are using the method as it is now. What do you think? The main use case is probably formatting for displaying a value (in the GUI or in some kind of log file). So it may not be a problem? Benedikt > DurationFormatUtils#formatDurationHMS implementation does not correspond to Javadoc and vice versa > -------------------------------------------------------------------------------------------------- > > Key: LANG-1004 > URL: https://issues.apache.org/jira/browse/LANG-1004 > Project: Commons Lang > Issue Type: Bug > Components: lang.text.* > Affects Versions: 3.3.2 > Reporter: Michael Osipov > Fix For: Patch Needed > > Attachments: LANG-1004.patch > > > This method has several flaws: > 1. Javadoc says: "The format used is ISO8601-like: H:m:s.S." but the method call supplies "H:mm:ss.SSS" > 2. ISO time never omits leading zeros, so the proper pattern must be "HH:mm:ss.SSS" > 3. The method name says: "HMS" but includes the second fraction. > Since the use of fractions is optional, the method should use "HH:mm:ss" and update the Javadoc as well. -- This message was sent by Atlassian JIRA (v6.2#6252)