Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 17 Oct 2013 07:49:42 +0000 (UTC)
From: "Henri Yandell (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12528732.1319567331985.78871.1381996182772@arcas>
In-Reply-To: <JIRA.12528732.1319567331985@arcas>
References: <JIRA.12528732.1319567331985@arcas>
Subject: [jira] [Commented] (LANG-763) Reintroduce DateUtils.UTC_TIME_ZONE
 constant
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/LANG-763?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137976=
96#comment-13797696 ]=20

Henri Yandell commented on LANG-763:
------------------------------------

This seems fair. I notice that Joda Time has a UTC constant (http://joda-ti=
me.sourceforge.net/apidocs/org/joda/time/DateTimeZone.html#UTC).

Patch desired for an immutable UTC constant.

> Reintroduce DateUtils.UTC_TIME_ZONE constant
> --------------------------------------------
>
>                 Key: LANG-763
>                 URL: https://issues.apache.org/jira/browse/LANG-763
>             Project: Commons Lang
>          Issue Type: New Feature
>          Components: lang.time.*
>    Affects Versions: 3.0.1
>            Reporter: Attila Kir=C3=A1ly
>            Priority: Minor
>             Fix For: Patch Needed
>
>
> In LANG-691 DateUtils.UTC_TIME_ZONE was removed because TimeZone-s are mu=
table. However it was a handy constant. So it would be nice if it could be =
reintroduced in an immutable way. For example:
> - by creating a new static method DateUtils.utcTimeZone() {return TimeZon=
e.getTimeZone("GMT");}
> - or by creating an immutable timezone type (subclassing maybe SimpleTime=
Zone)


--
This message was sent by Atlassian JIRA
(v6.1#6144)