Ernie Rael created LOG4J2-3420:
--
Summary: getlogger() UnsupportedOperationException when loaded by
Class.forName()
Key: LOG4J2-3420
URL: https://issues.apache.org/jira/browse/LOG4J2-3420
Project: Log4j
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ragini Chandrakant Gawande updated LOG4J2-3419:
---
Description:
Unable to create custom logging level using log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ragini Chandrakant Gawande updated LOG4J2-3419:
---
Description:
Unable to create custom logging level using log4j 2
Ragini Chandrakant Gawande created LOG4J2-3419:
--
Summary: Unable to create custom logging level using log4j 2
Bridge API
Key: LOG4J2-3419
URL: https://issues.apache.org/jira/browse/LOG4J2-3419
dependabot[bot] opened a new pull request #779:
URL: https://github.com/apache/logging-log4j2/pull/779
Bumps
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
from 2.9 to 3.2.2.
Commits
dependabot[bot] opened a new pull request #778:
URL: https://github.com/apache/logging-log4j2/pull/778
Bumps [maven-scm-plugin](https://github.com/apache/maven-scm) from 1.9.5 to
1.12.2.
Commits
jvz commented on pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775#issuecomment-1054492286
I think one possibility would be to add an interface in log4j-api for
loading properties and the general LoggerContext-specific properties. Then we
can move the parsing logic
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498835#comment-17498835
]
Gary D. Gregory edited comment on LOG4J2-3417 at 2/28/22, 10:47 AM:
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498835#comment-17498835
]
Gary D. Gregory commented on LOG4J2-3417:
-
Excellent. As long as we do reuse Log4j 2's runtime,
ppkarwasz commented on pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775#issuecomment-1054014736
@rgoers: isn't the properties format enough for your properties enhancement?
`log4j-core` just needs to provide a `PropertySource` for the JSON format.
IMHO
ppkarwasz opened a new pull request #777:
URL: https://github.com/apache/logging-log4j2/pull/777
This PR adds support for the `spring.factories` registration method of the
`Log4j2CloudConfigLoggingSystem` to replace the old Java system properties
injection method.
A Log4j 2.x
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498748#comment-17498748
]
Sagar Salal edited comment on LOG4J2-3416 at 2/28/22, 8:06 AM:
---
[~rgoers]
12 matches
Mail list logo