Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C670C9DAB for ; Wed, 25 Jan 2012 22:49:55 +0000 (UTC) Received: (qmail 48118 invoked by uid 500); 25 Jan 2012 22:49:55 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 47995 invoked by uid 500); 25 Jan 2012 22:49:54 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 47980 invoked by uid 99); 25 Jan 2012 22:49:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2012 22:49:54 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gudnabrsam@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-pz0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2012 22:49:48 +0000 Received: by dajs34 with SMTP id s34so32501404daj.30 for ; Wed, 25 Jan 2012 14:49:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=R6mJGw7G8azqGbLHmrmE1eg0Ip0x9ZWdvn82mhEY07g=; b=bQ/BeHawxUeoi6mGhEKlyOdEQ1MV9gVSnjrjXiXd8XKjDS+etWkxzy7AFgmHKFgM1f 9bJ63tDW232NTBYNYm4yz/XGNlT6QWp5QaM2KzX/SqnbfbqZQNdGVfCcjymBuDwW/kA5 OdcOgDU7Ad01ldUT3LjbRZIipHJnVkfVBp5xA= MIME-Version: 1.0 Received: by 10.68.74.164 with SMTP id u4mr2324797pbv.85.1327531767597; Wed, 25 Jan 2012 14:49:27 -0800 (PST) Received: by 10.68.42.69 with HTTP; Wed, 25 Jan 2012 14:49:27 -0800 (PST) Reply-To: gudnabrsam@gmail.com In-Reply-To: References: <4F20633E.3010504@systemoutprintln.de> Date: Wed, 25 Jan 2012 16:49:27 -0600 Message-ID: Subject: Re: [lang] What about Duration class? (org.apache.commons.lang.time) From: Matt Benson To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 25, 2012 at 4:14 PM, Christian Grobmeier wrote: > On Wed, Jan 25, 2012 at 9:17 PM, Benedikt Ritter > wrote: >>> But i found only discussions about duration& =A0joda-time dated 2004. >>> >>> (http://markmail.org/thread/733yqv5zwzsngj3j) >>> Now i really need in Duration functionality (especially such as >>> Duration.parse(String)). >>> >> I heard about joda-time a while ago. My impression is, that the joda pro= ject >> is not that active anymore (please correct me, if I'm wrong). So I would >> vouch for additions to lang regarding durations. What I'm also really >> missing in lang.time is conversation of durations. For example: >> DurationUtils.convertToMinutes(long seconds). > > Joda Time is imho a great lib. Before a few weeks I replaced all the > JDK stuff with Joda and it really saved my life. There was a release > in July 2011 or so and my impression is more this lib is stable and > does not need many releases. Actually I can't imagine a feature I miss > in Joda at the moment. > >> >>> I don't understand the Commons point on this issue. >>> >>> - Commons Lang doesn't need in own implementation of this >>> functionality and you suggest use joda-time? >>> - Commons Lang needs in simple& =A0lightweight implementation of Durati= on? >>> >>> Also i cannot find correspond issue in jira (but Eric Crampton in 2004 >>> wrote about >>> "Commons Lang task list that there is a need for DateRange/Duration >>> classes"). >> >> As you said, it is a while ago, since this was discussed. So let's revie= w >> this topic again. >> >> What are your thoughts? > > Hen (who is mainly behind lang) and Gary already mentioned, they don't > want to replicate Joda code into [lang]. I don't see any reasons why > we should do that now. Instead I would prefer to mark the time package > as deprecated and point users to joda. time does rely on jdk classes > and as I have found out by own experience, it is dangerous to work > with them. If you need any more reasons to use joda-time, consider its primary author, Stephen Colebourne: 1. Stephen is a Commons developer in any event; an Apache pedigree is not reason enough to duplicate his work here, but if we did, the resulting library would probably look like joda-time! 2. Stephen is also one of the key experts behind JSR-310 aka threeten, thus the future of dates and times in Java is already heavily based on the design of and lessons learned from joda-time. Matt > > Cheers > Christian > >> >> Regards >> Benedikt >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org