[
https://issues.apache.org/jira/browse/LOG4J2-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168443#comment-17168443
]
Ralph Goers commented on LOG4J2-241:
We have had requests in this area so leaving thi
[
https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-238.
Resolution: Abandoned
Marking as resolved/abandoned due to lack of activity.
> OSGi dependency fai
[
https://issues.apache.org/jira/browse/LOG4J2-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-191.
Resolution: Abandoned
Marking as resolved/abandoned due to lack of activity.
> Improve plugin uniq
[
https://issues.apache.org/jira/browse/LOG4J2-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-170.
Resolution: Fixed
These have been fixed in the latest versions of the log4j schema.
> Schema valid
cremor commented on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666928536
> I'm wondering what's to be done about `develop`, ie are there other
commits on that branch which should be of interest
Most of the latest commits on develop are from
[
https://issues.apache.org/jira/browse/LOG4J2-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2064.
-
Resolution: Won't Do
I have come to the conclusion that we don't want to release log4j-server. I
[
https://issues.apache.org/jira/browse/LOG4J2-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2512.
-
Resolution: Cannot Reproduce
Log4j 2.8.1 is very old and there has been no follow-up on this iss
[
https://issues.apache.org/jira/browse/LOG4J2-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2820.
-
Resolution: Information Provided
Marking as resolved since no other questions have been asked (a
[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168387#comment-17168387
]
Ralph Goers edited comment on LOG4J2-2901 at 7/31/20, 4:37 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168387#comment-17168387
]
Ralph Goers commented on LOG4J2-2901:
-
@Dejan Can you configure a service with -Dlog
[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168386#comment-17168386
]
Ralph Goers edited comment on LOG4J2-2901 at 7/31/20, 4:28 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168386#comment-17168386
]
Ralph Goers commented on LOG4J2-2901:
-
Have you tried with 2.13.3? I have configured
[
https://issues.apache.org/jira/browse/LOG4J2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2792.
-
Fix Version/s: 2.14.0
Resolution: Fixed
Based on my findings and the changes made in LOG4
[
https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2880.
-
Fix Version/s: 2.14.0
Resolution: Fixed
I can't say whether the JDK has a problem or not,
[
https://issues.apache.org/jira/browse/LOG4J2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2883.
-
Fix Version/s: 2.14.0
Resolution: Fixed
Thanks for the good unit test. From that I was ab
[
https://issues.apache.org/jira/browse/LOG4J2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168379#comment-17168379
]
ASF subversion and git services commented on LOG4J2-2883:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168380#comment-17168380
]
ASF subversion and git services commented on LOG4J2-2883:
-
Commi
rgoers commented on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-57635
Is there a tag included in the PR with the version number? Can those even be
added in a PR. If not it is a simple matter to tag the version associated with
this I guess.
[
https://issues.apache.org/jira/browse/LOG4J2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168131#comment-17168131
]
Ralph Goers commented on LOG4J2-2792:
-
Any feedback?
> Performance issue in log4j 2
fluffynuts edited a comment on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666570166
@rgoers I'm happy to follow up on the CVE and the recent email on the
mailing list
As for (2), I thought that's what this PR was, so am I correct in saying
fluffynuts commented on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666570166
@rgoers I'm happy to follow up on the CVE and the recent email on the
mailing list
As for (2), I thought that's what this branch was, so am I correct in saying
tha
[
https://issues.apache.org/jira/browse/LOG4J2-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2875.
-
Fix Version/s: 2.14.0
Resolution: Fixed
The parent directories were not being created for
[
https://issues.apache.org/jira/browse/LOG4J2-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168106#comment-17168106
]
ASF subversion and git services commented on LOG4J2-2875:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168107#comment-17168107
]
ASF subversion and git services commented on LOG4J2-2875:
-
Commi
rgoers commented on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666550770
@fluffynuts In answer to 1) as you know the main problem with the log4net
project is that all the active developers on it have left the project. So the
accepted workflow is u
[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167878#comment-17167878
]
Tamas Nemeth commented on LOG4J2-2901:
--
I have a similar issue. I have a a composit
carterkozak commented on pull request #329:
URL: https://github.com/apache/logging-log4j2/pull/329#issuecomment-666316087
Looking at this again, I think I should extract the predicate for classes
which can't be loaded to a separate change. It should be generally helpful
because the cost of
jvz commented on pull request #1:
URL: https://github.com/apache/logging-parent/pull/1#issuecomment-665859627
@dependabot merge
This is an automated message from the Apache Git Service.
To respond to the message, please log o
dependabot[bot] opened a new pull request #1:
URL: https://github.com/apache/logging-parent/pull/1
Bumps [apache](https://github.com/apache/maven-apache-parent) from 19 to 23.
Commits
See full diff in https://github.com/apache/maven-apache-parent/commits";>compare
view
dependabot[bot] merged pull request #1:
URL: https://github.com/apache/logging-parent/pull/1
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
dependabot[bot] closed pull request #370:
URL: https://github.com/apache/logging-log4j2/pull/370
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
dependabot[bot] opened a new pull request #393:
URL: https://github.com/apache/logging-log4j2/pull/393
Bumps [jetty-util](https://github.com/eclipse/jetty.project) from
8.2.0.v20160908 to 9.4.31.v20200723.
Commits
https://github.com/eclipse/jetty.project/commit/450ba27947e13e6
fluffynuts commented on pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666058294
@jvz thanks, two questions though:
1. The query about the CVE fix in this thread: that commit is on `develop`
-- I'm not sure of the workflow that is accepted on th
dependabot[bot] commented on pull request #370:
URL: https://github.com/apache/logging-log4j2/pull/370#issuecomment-666089626
Superseded by #393.
This is an automated message from the Apache Git Service.
To respond to the mes
jvz merged pull request #61:
URL: https://github.com/apache/logging-log4net/pull/61
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 to go to
35 matches
Mail list logo
