Chainsaw has been in limbo for far too long. There really is only 1 active
committer on the project and he has been telling people to use the latest code
in master in production, which is not acceptable by the Apache release policy.
We either need to have a release performed by the time of the n
I'll try to put in a fix for
https://issues.apache.org/jira/browse/LOG4J2-1988?filter=-1
(java.util.ConcurrentModificationException with AsyncLogger?) today.
Stretch goal: https://issues.apache.org/jira/browse/LOG4J2-2031 (Messages
appear out of order in log file (was: Log4j2 log file not refl
That all sounds great!
Gary
On Thu, Sep 14, 2017 at 1:33 PM, Matt Sicker wrote:
> I think we should release 2.9.1. If Ralph doesn't have time this weekend, I
> can RM.
>
> I have a feature (system properties/environment variables normalization)
> I'd like to add to 2.10 and am waiting for our b
I plan on doing the release build this weekend. Please hold off on merging new
features until after that. I agree with your plan.
Ralph
> On Sep 14, 2017, at 12:09 PM, Mikael Ståldal wrote:
>
> So do we plan to release 2.9.1 soon? Should we wait with merging new features
> into master?
>
> I
[
https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166911#comment-16166911
]
Mikael Ståldal commented on LOG4J2-2034:
Yes, the StatusLogger can be configured,
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
@mdvorak The code looks fine to me. But we will wait a while before
merging, since we plan to do a 2.9.1 bugfix release soon. This will go into
2.10.0.
---
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
@mdvorak I think that we should not care so much about garbage and micro
optimizations in the Jackson based layouts, since they are far from
garbage-free or optimal anyway.
Kee
I think we should release 2.9.1. If Ralph doesn't have time this weekend, I
can RM.
I have a feature (system properties/environment variables normalization)
I'd like to add to 2.10 and am waiting for our bugfixes first.
On 14 September 2017 at 14:09, Mikael Ståldal wrote:
> So do we plan to rel
Github user mdvorak commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
@mikaelstaldal Yeah i figured after digging deeper. Implemented it with
correct support.
Only thing that bugs me is that dynamically created LinkedHashMap - thats
wasteful and expens
So do we plan to release 2.9.1 soon? Should we wait with merging new
features into master?
I think it would be good to release 2.9.1 before the Java 9 release on
September 21th, since we have fixed a few Java 9 related issues.
Then we should wait for the Java 9 release, and test Log4j 2.9.1 w
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
@mdvorak Resolving `${}` expressions during serialization is necessary to
support dynamic lookups which depend on the current log event, such as
[ContextMapLookup](https://logging.apach
[
https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-2051:
-
Description:
Update Convertant Disruptor from 1.2.10 to 1.2.11.
This requires Java 8. Java 7 is
Gary Gregory created LOG4J2-2051:
Summary: Update Convertant Disruptor from 1.2.10 to 1.2.11.
Key: LOG4J2-2051
URL: https://issues.apache.org/jira/browse/LOG4J2-2051
Project: Log4j 2
Issue Ty
[
https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-2051:
-
Summary: Update Conversant Disruptor from 1.2.10 to 1.2.11. (was: Update
Convertant Disruptor fr
Github user EbenZhang commented on the issue:
https://github.com/apache/logging-log4net/pull/13
Added couple of unit tests for the subfolder. In order to easily write new
unit tests, I did some refactoring.
---
[
https://issues.apache.org/jira/browse/LOG4J2-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166192#comment-16166192
]
Gary Gregory commented on LOG4J2-2050:
--
That question does come up regularly, but we
[
https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166120#comment-16166120
]
ASF GitHub Bot commented on LOG4J2-1864:
Github user codescale commented on the i
Github user codescale commented on the issue:
https://github.com/apache/logging-log4j2/pull/62
Thanks @jvz for extending the documentation :+1:
https://github.com/apache/logging-log4j2/commit/af2dd30e16cece20b4ae475da851c8538bfa8879
---
Github user mdvorak commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
Partially, log4j-core completed successfully including all tests, whole
project failed somewhere on Cassandra with some JNI exception. I did not look
further into that yet. Does not seem rela
[
https://issues.apache.org/jira/browse/LOG4J2-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165894#comment-16165894
]
Remko Popma commented on LOG4J2-2050:
-
Thanks Matt, I was looking for snapshot builds
20 matches
Mail list logo
