jvz opened a new pull request, #1863:
URL: https://github.com/apache/logging-log4j2/pull/1863
This adds `ConfigurationChangeListener` and `ConfigurationChangeEvent` to
replace the use of `java.beans.PropertyChangeListener` and
`java.beans.PropertyChangeEvent` respectively. This removes the
jvz commented on PR #1401:
URL: https://github.com/apache/logging-log4j2/pull/1401#issuecomment-1763515200
Besides the merge conflict, I think you should take a look at the updated DI
system to see if it fits in with the lifecycles you need.
--
This is an automated message from the
jvz commented on issue #1520:
URL:
https://github.com/apache/logging-log4j2/issues/1520#issuecomment-1763512965
Fixed.
--
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 the specific comment.
To
jvz closed issue #1520: Reproducibility of `Log4jPlugins.java`
URL: https://github.com/apache/logging-log4j2/issues/1520
--
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 the specific comment.
To
jvz commented on issue #1520:
URL:
https://github.com/apache/logging-log4j2/issues/1520#issuecomment-1763512183
This is a regression that was otherwise address in 2.x in
https://issues.apache.org/jira/browse/LOG4J2-2735
--
This is an automated message from the Apache Git Service.
To
jvz commented on issue #1520:
URL:
https://github.com/apache/logging-log4j2/issues/1520#issuecomment-1763512001
Seems to be a regression from LOG4J-2735, but I can't see that issue on Jira
for some reason.
--
This is an automated message from the Apache Git Service.
To respond to the
jvz commented on issue #1520:
URL:
https://github.com/apache/logging-log4j2/issues/1520#issuecomment-1763496586
Well, this could be fixed fairly easily: alphabetize the entries before
writing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
jvz commented on issue #1841:
URL:
https://github.com/apache/logging-log4j2/issues/1841#issuecomment-1763491516
If you mean the general Spring Boot properties `logging.level.[logger-name]:
off`, then this is specific to however Spring decided to handle this particular
YAML parser. If this
[
https://issues.apache.org/jira/browse/LOG4J2-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3496.
-
Resolution: Fixed
This was generally implemented in {{InstanceFactory}} through various
ppkarwasz commented on issue #1778:
URL:
https://github.com/apache/logging-log4j2/issues/1778#issuecomment-1763476304
Many of our tests were written copying other tests, which also means, they
write to the same files, they use the same ports, etc. Therefore to achieve
this goal it was
swebb2066 commented on PR #271:
URL: https://github.com/apache/logging-log4cxx/pull/271#issuecomment-1763352390
Yes, I suggest 'EVENTS_AT_EXIT' conveys more meaning than 'INFINTELIFETIME'?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
vopl commented on PR #271:
URL: https://github.com/apache/logging-log4cxx/pull/271#issuecomment-1763350498
> +| -DLOG4CXX_EVENTS_AT_EXIT=ON | Prevent
@swebb2066, do you propose to rename
ppkarwasz commented on PR #1857:
URL: https://github.com/apache/logging-log4j2/pull/1857#issuecomment-1763323889
@dependabot recreate
--
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 the specific
13 matches
Mail list logo
