[jira] [Commented] (LOG4J2-2982) Use {@systemProperty} javadoc tag

[ https://issues.apache.org/jira/browse/LOG4J2-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255177#comment-17255177 ] Ralph Goers commented on LOG4J2-2982: - Yeah - that isn't likely.  > Use {@systemProperty} javadoc

[GitHub] [logging-log4j2] garydgregory commented on pull request #451: Remove unbound return type from Logger.getMessageFactory()

garydgregory commented on pull request #451: URL: https://github.com/apache/logging-log4j2/pull/451#issuecomment-751418152 This will break source compatibility though. This is an automated message from the Apache Git

[jira] [Commented] (LOG4J2-2982) Use {@systemProperty} javadoc tag

[ https://issues.apache.org/jira/browse/LOG4J2-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255155#comment-17255155 ] Gary D. Gregory commented on LOG4J2-2982: - That would require that we generate Javadocs with

[jira] [Created] (LOG4J2-2982) Use {@systemProperty} javadoc tag

Marcono1234 created LOG4J2-2982: --- Summary: Use {@systemProperty} javadoc tag Key: LOG4J2-2982 URL: https://issues.apache.org/jira/browse/LOG4J2-2982 Project: Log4j 2 Issue Type: Improvement

[GitHub] [logging-log4j2] Marcono1234 opened a new pull request #451: Remove unbound return type from Logger.getMessageFactory()

Marcono1234 opened a new pull request #451: URL: https://github.com/apache/logging-log4j2/pull/451 Commit 2e9fdc135545eee435cad14ee9d74101c93694be added the unbound return type to allow easier usage with `MessageFactory2`. However, an unbound return type causes loss of type safety: You

[jira] [Commented] (LOGCXX-507) Data race on LevelPtr when using the async appender

[ https://issues.apache.org/jira/browse/LOGCXX-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255149#comment-17255149 ] Robert Middleton commented on LOGCXX-507: - I just tested this with current master(no

[GitHub] [logging-log4cxx] rm5248 opened a new pull request #46: LOGCXX-324 Split up large syslog messages

rm5248 opened a new pull request #46: URL: https://github.com/apache/logging-log4cxx/pull/46 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[jira] [Commented] (LOGCXX-507) Data race on LevelPtr when using the async appender

[ https://issues.apache.org/jira/browse/LOGCXX-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255119#comment-17255119 ] Thorsten Schöning commented on LOGCXX-507: -- So what's your suggestion in the end, directly

[jira] [Comment Edited] (LOGCXX-507) Data race on LevelPtr when using the async appender

[ https://issues.apache.org/jira/browse/LOGCXX-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255066#comment-17255066 ] Robert Middleton edited comment on LOGCXX-507 at 12/26/20, 5:05 PM: I

[jira] [Commented] (LOGCXX-507) Data race on LevelPtr when using the async appender

[ https://issues.apache.org/jira/browse/LOGCXX-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255066#comment-17255066 ] Robert Middleton commented on LOGCXX-507: - I tested this out today, and the data race is possibly

[jira] [Commented] (LOGCXX-486) Replace ObjectPtr with more standard shared_ptr.

[ https://issues.apache.org/jira/browse/LOGCXX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255065#comment-17255065 ] Robert Middleton commented on LOGCXX-486: - I've updated a (new) proof-of-concept that all seems

[jira] [Created] (LOG4J2-2981) OnStartupTriggeringPolicy only rolls over when minsize = 0

Samuel Martin created LOG4J2-2981: - Summary: OnStartupTriggeringPolicy only rolls over when minsize = 0 Key: LOG4J2-2981 URL: https://issues.apache.org/jira/browse/LOG4J2-2981 Project: Log4j 2