Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 44330 invoked from network); 4 Feb 2008 18:49:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2008 18:49:33 -0000 Received: (qmail 55488 invoked by uid 500); 4 Feb 2008 18:49:23 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 55410 invoked by uid 500); 4 Feb 2008 18:49:23 -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 55401 invoked by uid 99); 4 Feb 2008 18:49:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 10:49:23 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 18:49:16 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E525D714076 for ; Mon, 4 Feb 2008 10:49:08 -0800 (PST) Message-ID: <26105810.1202150948934.JavaMail.jira@brutus> Date: Mon, 4 Feb 2008 10:49:08 -0800 (PST) From: "Matt Benson (JIRA)" To: issues@commons.apache.org Subject: [jira] Commented: (LANG-362) Add ExtendedMessageFormat to org.apache.commons.lang.text In-Reply-To: <23838880.1193088290565.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/LANG-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565464#action_12565464 ] Matt Benson commented on LANG-362: ---------------------------------- IMO that's not important. I think those methods are intended for setup rather than a runtime (i.e. after the dropping-in has taken place). I would be quite surprised to find client code that used these methods at a level lower than configuration, where I would expect the substitution to take place. If it becomes an issue we could add an option to ignore the calls rather than throwing Exceptions. > Add ExtendedMessageFormat to org.apache.commons.lang.text > --------------------------------------------------------- > > Key: LANG-362 > URL: https://issues.apache.org/jira/browse/LANG-362 > Project: Commons Lang > Issue Type: New Feature > Reporter: Matt Benson > Assignee: Matt Benson > Priority: Minor > Fix For: 2.4 > > Attachments: DateFormatFactory.java, extendedMessageFormat.patch.txt, extendedMessageFormat.patch.txt, ExtendedMessageFormat2.java, FormatFactory.java > > > Discussed on dev@ ( http://mail-archives.apache.org/mod_mbox/commons-dev/200710.mbox/%3c590921.30381.qm@web55103.mail.re4.yahoo.com%3e ); adding here for tracking purposes and in case anyone has any serious objections to my implementation. Patch forthcoming... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.