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

ASF GitHub Bot commented on FLUME-3296:
---------------------------------------

GitHub user szaboferee opened a pull request:

    https://github.com/apache/flume/pull/253

    FLUME-3296 Revert log4j 2 upgrade on 1.9 branch

    Changing log4j2 to log4j to keep compatibility

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/szaboferee/flume FLUME-3296

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flume/pull/253.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #253
    
----
commit 172bbc95785adabc7cda14b525cdead49bd056cd
Author: turcsanyi <turcsanyi@...>
Date:   2018-11-23T12:12:06Z

    FLUME-3296 Revert deleted log4j.properties files.

commit 609dc51bd3ccdf8759dc58c4c41c1b520c6606db
Author: turcsanyi <turcsanyi@...>
Date:   2018-11-23T12:18:08Z

    FLUME-3296 Fix http-sink log4j.properties.

commit af84791f220a0f08c76dfbe22dacb2d8f7606448
Author: turcsanyi <turcsanyi@...>
Date:   2018-11-23T12:43:34Z

    FLUME-3296 Remove log4j2.xml files.

commit 84a5acbc4a0de14cde1a60f496d0d9b879fac077
Author: turcsanyi <turcsanyi@...>
Date:   2018-11-23T15:01:41Z

    FLUME-3296 Revert from log4j2 to log4j in pom-s.

----


> Revert log4j 2 upgrade on 1.9 branch
> ------------------------------------
>
>                 Key: FLUME-3296
>                 URL: https://issues.apache.org/jira/browse/FLUME-3296
>             Project: Flume
>          Issue Type: Sub-task
>            Reporter: Ferenc Szabo
>            Assignee: Peter Turcsanyi
>            Priority: Major
>             Fix For: 1.9.0
>
>




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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to