You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2018/01/19 04:35:01 UTC

[jira] [Commented] (LOG4J2-2199) Move ProcessIdUtil out of log4j-api into log4j-core

    [ https://issues.apache.org/jira/browse/LOG4J2-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331727#comment-16331727 ] 

Ralph Goers commented on LOG4J2-2199:
-------------------------------------

Moving ProcessIdUtil to Log4j core, while the right thing to do, will not fix LOG4J2-2038 or LOG4J2-2133.

> Move ProcessIdUtil out of log4j-api into log4j-core
> ---------------------------------------------------
>
>                 Key: LOG4J2-2199
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2199
>             Project: Log4j 2
>          Issue Type: Task
>          Components: API, Core
>    Affects Versions: 2.10.0
>            Reporter: Remko Popma
>            Priority: Major
>
> Now that there is a separate log4j-core-java9 and log4j-core is a multi-release jar, we can move {{ProcessIdUtil}} out of log4j-api into log4j-core.
> Hopefully this will fix LOG4J2-2038 and LOG4J2-2133.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)