[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660035#comment-16660035 ] Robert Ross commented on LOG4J2-2484: - That's a reasonable concise summation. > Allow setting of

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660001#comment-16660001 ] Remko Popma commented on LOG4J2-2484: - Ok, so the problem is that the application also uses STDERR

Jenkins build is back to stable : Log4j 2 3.x #260

See

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659953#comment-16659953 ] Robert Ross commented on LOG4J2-2484: - Thanks for the clarification on use case.  Let's try this:

Jenkins build is still unstable: Log4j 2 3.x #259

See

Jenkins build is back to stable : Log4j 2 2.x #3670

See

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659915#comment-16659915 ] Remko Popma commented on LOG4J2-2484: - Interesting, thank you for that. What I mean by use case is

[jira] [Comment Edited] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659898#comment-16659898 ] Robert Ross edited comment on LOG4J2-2484 at 10/23/18 1:03 AM: --- For more

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659898#comment-16659898 ] Robert Ross commented on LOG4J2-2484: - For more clarification on POSIX guidance:

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659894#comment-16659894 ] Robert Ross commented on LOG4J2-2484: - Personally, I think you're misinterpreting "for writing

[jira] [Comment Edited] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659890#comment-16659890 ] Remko Popma edited comment on LOG4J2-2484 at 10/23/18 12:40 AM: {quote}

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659890#comment-16659890 ] Remko Popma commented on LOG4J2-2484: - {quote} Can you point me to where it is documented as a

[jira] [Comment Edited] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659843#comment-16659843 ] Robert Ross edited comment on LOG4J2-2484 at 10/22/18 11:51 PM: I

[jira] [Comment Edited] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659843#comment-16659843 ] Robert Ross edited comment on LOG4J2-2484 at 10/22/18 11:51 PM: I

[jira] [Comment Edited] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659843#comment-16659843 ] Robert Ross edited comment on LOG4J2-2484 at 10/22/18 11:50 PM: I

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659843#comment-16659843 ] Robert Ross commented on LOG4J2-2484: - **I changed the ticket to specifically avoid saying this

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659828#comment-16659828 ] Remko Popma commented on LOG4J2-2484: - Why is this a good idea? What’s the use case? By convention,

Jenkins build is still unstable: Log4j 2 2.x #3669

See

[jira] [Commented] (LOG4J2-2485) SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts

[ https://issues.apache.org/jira/browse/LOG4J2-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659722#comment-16659722 ] Gary Gregory commented on LOG4J2-2485: -- OK, good to know, thank you. > SizeBasedTriggeringPolicy

Jenkins build became unstable: Log4j 2 2.x #3668

See

[jira] [Commented] (LOG4J2-2485) SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts

[ https://issues.apache.org/jira/browse/LOG4J2-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659677#comment-16659677 ] Giovanni Matteo Fumarola commented on LOG4J2-2485: -- The same thing happened with

[jira] [Commented] (LOG4J2-2485) SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts

[ https://issues.apache.org/jira/browse/LOG4J2-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659654#comment-16659654 ] Gary Gregory commented on LOG4J2-2485: -- You should use 2.11.1 instead of 2.11.0 so the code is

[GitHub] logging-log4j2 issue #222: LOG4J2-2482 BasicContextSelector cannot be used i...

Github user rgansevles commented on the issue: https://github.com/apache/logging-log4j2/pull/222 Pull-request was applied ---

[jira] [Commented] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659648#comment-16659648 ] ASF GitHub Bot commented on LOG4J2-2482: Github user rgansevles commented on the issue:

[jira] [Commented] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659647#comment-16659647 ] ASF GitHub Bot commented on LOG4J2-2482: Github user rgansevles closed the pull request at:

[GitHub] logging-log4j2 pull request #222: LOG4J2-2482 BasicContextSelector cannot be...

Github user rgansevles closed the pull request at: https://github.com/apache/logging-log4j2/pull/222 ---

[jira] [Updated] (LOG4J2-2485) SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts

[ https://issues.apache.org/jira/browse/LOG4J2-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated LOG4J2-2485: - Description: We are working on migrate Log4J to Log4J2 in Hadoop

[jira] [Created] (LOG4J2-2485) SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts

Giovanni Matteo Fumarola created LOG4J2-2485: Summary: SizeBasedTriggeringPolicy is not honored when using the DirectWriteRolloverStrategy if the machine restarts Key: LOG4J2-2485 URL:

Jenkins build became unstable: Log4j 2 3.x #258

See

[jira] [Comment Edited] (LOG4J2-2476) org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659512#comment-16659512 ] Gary Gregory edited comment on LOG4J2-2476 at 10/22/18 7:26 PM: Applied

[jira] [Resolved] (LOG4J2-2476) org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2476. -- Resolution: Fixed Fix Version/s: 2.11.2 3.0.0 Applied PR as is to

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659509#comment-16659509 ] ASF subversion and git services commented on LOG4J2-2476: - Commit

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659503#comment-16659503 ] ASF subversion and git services commented on LOG4J2-2476: - Commit

[jira] [Updated] (LOG4J2-2476) org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2476: - Summary: org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api (was:

[jira] [Commented] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659446#comment-16659446 ] Rob Gansevles commented on LOG4J2-2482: --- [~garydgregory] thanks for applying the pull request.  

[jira] [Closed] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Gansevles closed LOG4J2-2482. - > BasicContextSelector cannot be used in a OSGI application >

[jira] [Resolved] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2482. -- Resolution: Fixed Fix Version/s: 2.11.2 3.0.0 [~rgansevles]:

[jira] [Commented] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659402#comment-16659402 ] ASF subversion and git services commented on LOG4J2-2482: - Commit

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659369#comment-16659369 ] ASF GitHub Bot commented on LOG4J2-2476: GitHub user AlBundy33 opened a pull request:

[GitHub] logging-log4j2 pull request #223: [LOG4J2-2476] missing classes for 1.2 comp...

GitHub user AlBundy33 opened a pull request: https://github.com/apache/logging-log4j2/pull/223 [LOG4J2-2476] missing classes for 1.2 compatibility missing classes in 1.2-api These are needed to avoid compile-errors/NoClassDefFoundErrors with libraries that try to configure

[jira] [Closed] (LOG4NET-614) If LogicalThreadContext has a property with NULL value it causes an exception

[ https://issues.apache.org/jira/browse/LOG4NET-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner closed LOG4NET-614. --- Resolution: Duplicate Assignee: Dominik Psenner Fix Version/s: 2.1.0 Thanks

[jira] [Commented] (LOG4J2-2482) BasicContextSelector cannot be used in a OSGI application

[ https://issues.apache.org/jira/browse/LOG4J2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659261#comment-16659261 ] ASF subversion and git services commented on LOG4J2-2482: - Commit

[jira] [Commented] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659177#comment-16659177 ] Gary Gregory commented on LOG4J2-2484: -- Patches welcome! ;) > Allow setting of output stream on

Jenkins build is back to normal : Log4j 2 2.x #3663

See

[jira] [Updated] (LOG4J2-2484) Allow setting of output stream on StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Ross updated LOG4J2-2484: Summary: Allow setting of output stream on StatusLogger (was: Allow setting of output stream to

[jira] [Updated] (LOG4J2-2484) Allow setting of output stream to STDOUT for StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Ross updated LOG4J2-2484: Summary: Allow setting of output stream to STDOUT for StatusLogger (was: Allow setting of stream

[jira] [Created] (LOG4J2-2484) Allow setting of stream to STDOUT for StatusLogger

Robert Ross created LOG4J2-2484: --- Summary: Allow setting of stream to STDOUT for StatusLogger Key: LOG4J2-2484 URL: https://issues.apache.org/jira/browse/LOG4J2-2484 Project: Log4j 2 Issue

[jira] [Created] (LOG4J2-2483) CronTriggeringPolicy fails with $${date} in path

Stephen Dawkins created LOG4J2-2483: --- Summary: CronTriggeringPolicy fails with $${date} in path Key: LOG4J2-2483 URL: https://issues.apache.org/jira/browse/LOG4J2-2483 Project: Log4j 2

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659035#comment-16659035 ] Al Bundy commented on LOG4J2-2476: -- This seems to be a github issue. Currently ir seems to work. >

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659018#comment-16659018 ] Gary Gregory commented on LOG4J2-2476: -- I get a 404 on the link 

[jira] [Commented] (LOG4J2-2476) org.apache.log4j.SimpleLayout missing in log4j-1.2-api

[ https://issues.apache.org/jira/browse/LOG4J2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658978#comment-16658978 ] Al Bundy commented on LOG4J2-2476: -- I sent a PR but it is not displayed and if I try to send it again I