You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2018/01/29 16:32:00 UTC
[jira] [Work started] (LOG4J2-2224) Rename package
`core.util.datetime` to `core.time.internal`
[ https://issues.apache.org/jira/browse/LOG4J2-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on LOG4J2-2224 started by Remko Popma.
-------------------------------------------
> Rename package `core.util.datetime` to `core.time.internal`
> -----------------------------------------------------------
>
> Key: LOG4J2-2224
> URL: https://issues.apache.org/jira/browse/LOG4J2-2224
> Project: Log4j 2
> Issue Type: Task
> Components: Core, Layouts
> Affects Versions: 2.10.0
> Reporter: Remko Popma
> Assignee: Remko Popma
> Priority: Major
> Fix For: 2.11.0
>
>
> As discussed on the mailing list in relation to LOG4J2-1883, there’s a consensus that additional time related classes should not be added to the {{core.util}} package. Additionally, the Log4j community wants to start clarifying which classes are published and which classes are internal to Log4j2.
> The classes in the {{util.datetime}} package, although public, were never intended to be used directly by client code outside of Log4j. The hope is that the new package name clarifies the intended usage better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)