Argh, I pushed this to the wrong branch (master instead of develop) by
habit.
Sorry
Stefan
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4net/pull/11
---
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
Github user bodewig commented on the issue:
https://github.com/apache/logging-log4net/pull/11
merged, many thanks!
---
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 wis
GitHub user MarcelGosselin opened a pull request:
https://github.com/apache/logging-log4net/pull/11
(doc) Fix name of class LogicalThreadContext
Fix name of class LogicalThreadContext in Scopes section, words were
reversed.
You can merge this pull request into a Git repository by r
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067614#comment-16067614
]
Gary Gregory commented on LOG4J2-1950:
--
The test has JUnit Assume's to only run on J
You are correct. I was going to add it later but it got mixed up in this
commit. I just disabled it.
Thank you for noticing!
Gary
On Wed, Jun 28, 2017 at 9:47 AM, Matt Sicker wrote:
> That JMS stuff doesn't look like it belongs here?
>
> On 27 June 2017 at 13:12, wrote:
>
> > Repository: logg
[
https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067595#comment-16067595
]
ASF subversion and git services commented on LOG4J2-1934:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15519381#comment-15519381
]
Remko Popma edited comment on LOG4J2-1611 at 6/29/17 1:39 AM:
-
This topic makes me think some sort of CircuitBreakerAppender may be useful
as an analogue to FailoverAppender. Instead of permanently failing over to
the backup appenders, this appender would eventually switch back to the
primary appender when it's safely back up. Supporting a full open/half
open/
Brilliant! :-)
Gary
On Wed, Jun 28, 2017 at 10:09 AM, Matt Sicker wrote:
> Oh, I missed the context line. It's part of the tag already.
>
> On 28 June 2017 at 12:02, Mikael Ståldal wrote:
>
> > I just did that, didn't I?
> >
> >
> >
> > On 2017-06-28 18:57, Gary Gregory wrote:
> >
> >> On Jun
Oh, I missed the context line. It's part of the tag already.
On 28 June 2017 at 12:02, Mikael Ståldal wrote:
> I just did that, didn't I?
>
>
>
> On 2017-06-28 18:57, Gary Gregory wrote:
>
>> On Jun 28, 2017 08:54, "Matt Sicker" wrote:
>>
>> You can add a @deprecated javadoc tag to specify that
[
https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1958:
---
Description:
Due to inherent security weakness of Java object serialization, see
https://www
I just did that, didn't I?
On 2017-06-28 18:57, Gary Gregory wrote:
On Jun 28, 2017 08:54, "Matt Sicker" wrote:
You can add a @deprecated javadoc tag to specify that which makes it more
prominent in the javadocs.
+1
Gary
On 28 June 2017 at 08:50, wrote:
Repository: logging-log4j2
Upda
On Jun 28, 2017 08:54, "Matt Sicker" wrote:
You can add a @deprecated javadoc tag to specify that which makes it more
prominent in the javadocs.
+1
Gary
On 28 June 2017 at 08:50, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/LOG4J2-1958 041f42dad -> 61db8afdd
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066847#comment-16066847
]
Matt Sicker commented on LOG4J2-1958:
-
Said status logger message might want to inclu
That JMS stuff doesn't look like it belongs here?
On 27 June 2017 at 13:12, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 93afa566c -> a5a95886b
>
>
> [LOG4J2-1699] Log File Permissions with PosixFilePermission feedback
> from jira. Closes #89.
> - item 2: Better
[
https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066829#comment-16066829
]
ASF GitHub Bot commented on LOG4J2-928:
---
Github user jvz commented on a diff in the
Github user jvz commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/87#discussion_r124592044
--- Diff:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/ThreadHints.java
---
@@ -0,0 +1,63 @@
+/*
+ * Licensed to the Apache So
You can add a @deprecated javadoc tag to specify that which makes it more
prominent in the javadocs.
On 28 June 2017 at 08:50, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/LOG4J2-1958 041f42dad -> 61db8afdd
>
>
> LOG4J2-1958 Specify version when SerializedLayout is depr
[
https://issues.apache.org/jira/browse/LOG4J2-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal resolved LOG4J2-1959.
Resolution: Fixed
In Git master.
> Disable DTD processing in XML configuration files
> ---
Mikael Ståldal created LOG4J2-1959:
--
Summary: Disable DTD processing in XML configuration files
Key: LOG4J2-1959
URL: https://issues.apache.org/jira/browse/LOG4J2-1959
Project: Log4j 2
Issue
In the manual pages, can we mention that in previous versions the default
was SerializedLayout, but as of log4j-2.9 users need to explicitly specify
a layout since there is no default? I think it is important to document the
log4j version when this change took place.
On Wed, Jun 28, 2017 at 9:52 P
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066491#comment-16066491
]
Mikael Ståldal commented on LOG4J2-1950:
Then something else might be wrong. Thos
[
https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066483#comment-16066483
]
Chris Slater commented on LOG4J2-1949:
--
Yes. I can create a patch.
> On failove
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066485#comment-16066485
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
The docker VM is configured {{FROM o
[
https://issues.apache.org/jira/browse/LOG4J2-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066477#comment-16066477
]
ASF GitHub Bot commented on LOG4J2-1725:
GitHub user phymbert opened a pull reque
GitHub user phymbert opened a pull request:
https://github.com/apache/logging-log4j2/pull/90
[LOG4J2-1725] RollingFileAppender's filePattern not reloaded
Reproduced and fixed, allow to update PatternProcessor of the reused
manager if configuration changed.
You can merge this pull r
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066445#comment-16066445
]
Mikael Ståldal commented on LOG4J2-1950:
{quote}SecureSocketAppenderSocketOptions
[
https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066437#comment-16066437
]
Mikael Ståldal commented on LOG4J2-1958:
See Git branch LOG4J2-1958.
> Deprecate
[
https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066411#comment-16066411
]
Mikael Ståldal commented on LOG4J2-1958:
Yes, that could be a good idea.
> Depre
[
https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1086:
-
Attachment: LOG4J2-1086.Test.patch
Hello [~ralph.go...@dslextreme.com] and team,
I am no
[
https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066120#comment-16066120
]
Pierrick HYMBERT commented on LOG4J2-1699:
--
OK for me, thank you all! Dear [~ddi
32 matches
Mail list logo
