See below.

> On Apr 11, 2022, at 7:18 PM, Tristan Stevens <tris...@apache.org> wrote:
> 
> Also, there's a couple of commits in that PR that we'll need to cherry pick
> regardless:
> 
> https://github.com/apache/flume/pull/351/commits/39042bd48047ad10038c0c13fb130c4455be8e8f
> which fixes a regression on command line arguments.

See PR comments
> 
> https://github.com/apache/flume/blob/31d99d3cd1a8ad531c2a16cb4a63d1a25d5a01db/conf/log4j2.xml
> This file fixes a regression in the default log behaviour for log4j2 Vs
> log4j2

This is incorrect. The default log4j.properties has logging to the console 
commented out. The log4j2 configuration is correct.

> 
> https://github.com/apache/flume/blob/ac262b23db72be418dc18c74c9d754ceb45dfe5d/flume-ng-tests/pom.xml
> Without this we don't get any log outputs in the build tests.
> 

This one looks correct.

> I can raise JIRAs and get the specific diffs added, probably this evening I
> would think.

Ralph

Reply via email to