I think there are some things in the pom files that are just copy paste
jobs from pom to pom. They could use a nice cleaning.
On 1 June 2017 at 17:29, Ralph Goers wrote:
> I have no idea what uses that or why it is there.
>
> Ralph
>
> > On Jun 1, 2017, at 2:48 PM, Gary Gregory wrote:
> >
> > H
I have no idea what uses that or why it is there.
Ralph
> On Jun 1, 2017, at 2:48 PM, Gary Gregory wrote:
>
> Hi All,
>
> My understanding is that for a Maven multi-module project to work, the
> folder name must equal the module name, which we do.
>
> What I do not get is what the property d
Hi All,
My understanding is that for a Maven multi-module project to work, the
folder name must equal the module name, which we do.
What I do not get is what the property defines in most of the
POMs are not equal to the folder name.
?
Gary
[
https://issues.apache.org/jira/browse/LOG4J2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1930.
Resolution: Fixed
Fix Version/s: 2.9
In Git master.
> Add forEach() methods to org.apache.l
[Wrong ML before]
Hi All,
I am adding the following methods to the MapMessage class:
org.apache.logging.log4j.message.MapMessage.forEach(BiConsumer)
org.apache.logging.log4j.message.MapMessage.forEach(TriConsumer, S)
that will simply delegate to the underlying map. This will avoid call sites
ca
Perhaps we need some kind of stress test here... this kind of failure gives
me the willies of seeing it in a production deployment.
Gary
On Jun 1, 2017 11:32 AM, "Matt Sicker" wrote:
> I'm pretty sure I've seen that same issue randomly before as well.
>
> On 1 June 2017 at 12:44, Ralph Goers w
I'm pretty sure I've seen that same issue randomly before as well.
On 1 June 2017 at 12:44, Ralph Goers wrote:
> I’ve seen that occasionally I think. No idea what it is about.
>
> Ralph
>
> > On Jun 1, 2017, at 9:42 AM, Gary Gregory wrote:
> >
> > Hi All:
> >
> > I've just had this random failu
Hi All,
It looks like:
org.apache.logging.log4j.message.MapMessage.newInstance(Map)
was supposed to be a static method.
Can't change it now I suppose :-( as it would break BC.
I wonder if we should start tracking these TODOs with // TODO Fix for 3.0
comments?
Gary
[
https://issues.apache.org/jira/browse/LOG4J2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033396#comment-16033396
]
ASF subversion and git services commented on LOG4J2-1930:
-
Commit
I’ve seen that occasionally I think. No idea what it is about.
Ralph
> On Jun 1, 2017, at 9:42 AM, Gary Gregory wrote:
>
> Hi All:
>
> I've just had this random failure:
>
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]
> AsyncLoggerThreadContextGarbageFreeTest>AbstractAsyncThreadCon
[
https://issues.apache.org/jira/browse/LOG4J2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1930:
-
Description:
Add {{forEach()}} methods to {{org.apache.logging.log4j.message.MapMessage}}
that d
[
https://issues.apache.org/jira/browse/LOG4J2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1930:
-
Description:
Add {{forEach()}} methods to {{org.apache.logging.log4j.message.MapMessage}}:
{code
Gary Gregory created LOG4J2-1930:
Summary: Add forEach() methods to
org.apache.logging.log4j.message.MapMessage
Key: LOG4J2-1930
URL: https://issues.apache.org/jira/browse/LOG4J2-1930
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033324#comment-16033324
]
ASF subversion and git services commented on LOG4J2-1294:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033307#comment-16033307
]
Gary Gregory commented on LOG4J2-1929:
--
Closes #78.
> EOFException with FormattedMe
[
https://issues.apache.org/jira/browse/LOG4J2-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1929.
Resolution: Fixed
In Git master; commit e89ac6e5b16d15497c12758665dbbfb1534eb13d.
> EOFException w
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/78
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/LOG4J2-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033301#comment-16033301
]
ASF subversion and git services commented on LOG4J2-1929:
-
Commit
Hi All:
I've just had this random failure:
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
AsyncLoggerThreadContextGarbageFreeTest>AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:162->AbstractAsyncThreadContextTestBase.checkResult:185
AsyncLoggerAndAsyncAppenderTest.log: line 0 expect
Gary Gregory created LOG4J2-1929:
Summary: EOFException with FormattedMessage
Key: LOG4J2-1929
URL: https://issues.apache.org/jira/browse/LOG4J2-1929
Project: Log4j 2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4J2-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033222#comment-16033222
]
Gary Gregory commented on LOG4J2-1294:
--
These last two comments got mixed up with [L
Github user jvz commented on the issue:
https://github.com/apache/logging-log4j2/pull/78
I've been pretty busy lately and haven't gotten to do anything on this
project in a little while. However, as mentioned, this PR can be merged by
anyone else. We don't have plans to release anytim
[
https://issues.apache.org/jira/browse/LOG4J2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Ventura Carro updated LOG4J2-1928:
Description:
Following the docs about
[RollingRandomAccessFileAppender|https://log
Lucas Ventura Carro created LOG4J2-1928:
---
Summary: RollingRandomAccessFileAppender with
DirectWriteRolloverStrategy requires a fileName
Key: LOG4J2-1928
URL: https://issues.apache.org/jira/browse/LOG4J2-1928
[
https://issues.apache.org/jira/browse/LOG4J2-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1927.
-
Resolution: Invalid
> Using Configurator.setLevel() results in a default LoggerConfig
> -
[
https://issues.apache.org/jira/browse/LOG4J2-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032836#comment-16032836
]
Ralph Goers commented on LOG4J2-1927:
-
Log4J already does this. It will look at the p
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032820#comment-16032820
]
ASF subversion and git services commented on LOG4J2-1926:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032817#comment-16032817
]
ASF subversion and git services commented on LOG4J2-1926:
-
Commit
GitHub user liyuj opened a pull request:
https://github.com/apache/logging-log4j2/pull/82
Add a new LuceneAppender which writes logging events to a lucene index
library.
Add a new LuceneAppender which writes logging events to a lucene index
library.The log4j2.xml configuration is a
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032785#comment-16032785
]
Remko Popma commented on LOG4J2-1926:
-
In SortedArrayStringMap we can replace Marshal
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1926:
Summary: Remove dependency on RMI and Management APIs from log4j-api (was:
Remove dependency on Ma
Github user bsokolovu commented on the issue:
https://github.com/apache/logging-log4j2/pull/78
Hi gatekeepers!
Are you going to merge it and use it? Or you have new comments? Or you just
forgot about it? ))
---
If your project is set up for it, you can reply to this email and ha
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032657#comment-16032657
]
Oleg Kalnichevski commented on LOG4J2-1926:
---
Remko,
The real question to me is
Thorkild Gregersen created LOG4J2-1927:
--
Summary: Using Configurator.setLevel() results in a default
LoggerConfig
Key: LOG4J2-1927
URL: https://issues.apache.org/jira/browse/LOG4J2-1927
Project:
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032626#comment-16032626
]
Remko Popma edited comment on LOG4J2-1926 at 6/1/17 8:19 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032626#comment-16032626
]
Remko Popma commented on LOG4J2-1926:
-
Ah, thanks. I see it now.
That one is trickie
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032568#comment-16032568
]
Oleg Kalnichevski commented on LOG4J2-1926:
---
o.a.l.log4j.message.ExtendedThread
37 matches
Mail list logo
