GitHub user liyuj opened a pull request:
https://github.com/apache/logging-log4j2/pull/74
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
Hi,
The vote is over and endet with a +1 from Gary, Stefan, Remko, Matt and me.
Mikael gave a 0. Therefore we are going to proceed with the migration from
svn to git of the log4net subproject.
Thanks for everyone who participated in the vote.
Dominik
On 19 Apr 2017 4:50 p.m., "Dominik Psenner"
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/68
---
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-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1885.
-
Resolution: Fixed
Fix Version/s: 2.9
Fixed in master. Please verify and close.
> document
[
https://issues.apache.org/jira/browse/LOG4J2-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-1885:
---
Assignee: Matt Sicker
> documentation error regarding additivity default value
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980491#comment-15980491
]
ASF subversion and git services commented on LOG4J2-1885:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980490#comment-15980490
]
Ralph Goers commented on LOG4J2-1031:
-
Here is what I posted on the mailing list at t
[
https://issues.apache.org/jira/browse/LOG4J2-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980489#comment-15980489
]
Matt Sicker commented on LOG4J2-1885:
-
The only reason you'd get duplicate logging wi
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/72
---
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-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980487#comment-15980487
]
Matt Sicker commented on LOG4J2-1802:
-
Remko has pointed out that [Asciidoctor|http:/
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980478#comment-15980478
]
ASF subversion and git services commented on LOG4J2-1855:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980474#comment-15980474
]
ASF subversion and git services commented on LOG4J2-1855:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980476#comment-15980476
]
ASF GitHub Bot commented on LOG4J2-1855:
Github user asfgit closed the pull reque
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980475#comment-15980475
]
ASF subversion and git services commented on LOG4J2-1855:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1855.
-
Resolution: Fixed
Fix Version/s: 2.9
Thanks for the PR! Merged to master. Please verify an
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980473#comment-15980473
]
ASF subversion and git services commented on LOG4J2-1855:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-1855:
---
Assignee: Matt Sicker
> Add an optional random delay in TimeBasedTriggeringPolicy
>
[
https://issues.apache.org/jira/browse/LOG4J2-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980472#comment-15980472
]
Matt Sicker commented on LOG4J2-1031:
-
The feature already exists for configuration f
[
https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980470#comment-15980470
]
ASF GitHub Bot commented on LOG4J2-1877:
Github user asfgit closed the pull reque
[
https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980469#comment-15980469
]
ASF subversion and git services commented on LOG4J2-1877:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980467#comment-15980467
]
Matt Sicker commented on LOG4J2-1877:
-
Gary, you merged this without the author info
[
https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980468#comment-15980468
]
ASF subversion and git services commented on LOG4J2-1877:
-
Commit
“I have too often seen APIs that seemed like a good idea at the time but
were, in fact, woefully deficient, baked into the Java Platform where they
fester for ages, cause pain to all who use it, and torment those who
maintain it. I will not let that happen
Here“ - Mark Reinhold
That sounds like J
On Apr 23, 2017 9:19 AM, "Matt Sicker" wrote:
One potential scenario I see is that many users may just end up disabling
JPMS in all their applications to the point that it's significantly revised
or scaled back for Java 10 or later.
That's my plan the first time I see an IllegalAccessError :-(
Oh, and I suppose this is a great time to gloat: if Java 9 turns out to be
a dud, there's always Scala and Kotlin as interesting alternatives to
continue the general Java platform. Depending on how this goes, it's even
possible that a company like IBM or Red Hat will fork Java into a new
language.
One potential scenario I see is that many users may just end up disabling
JPMS in all their applications to the point that it's significantly revised
or scaled back for Java 10 or later.
On 23 April 2017 at 11:04, Gary Gregory wrote:
> Worse: Are Java 9 modules its Titanic?
> https://developer.j
Worse: Are Java 9 modules its Titanic?
https://developer.jboss.org/blogs/scott.stark/2017/04/14/critical-deficiencies-in-jigsawjsr-376-java-platform-module-system-ec-member-concerns
Gary
On Apr 22, 2017 5:02 PM, "Ralph Goers" wrote:
> This is an interesting look at the problems faced in gettin
27 matches
Mail list logo