ppkarwasz commented on PR #1856:
URL: https://github.com/apache/logging-log4j2/pull/1856#issuecomment-1757166532
@Dreeam-qwq,
Take your time. We won't be able to include this PR into `2.21.0` anyway,
since the release process is already in motion.
You can also resubmit this PR
Dreeam-qwq closed pull request #1856: Support for disruptor-4.0.0
URL: https://github.com/apache/logging-log4j2/pull/1856
--
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 uns
Dreeam-qwq commented on PR #1856:
URL: https://github.com/apache/logging-log4j2/pull/1856#issuecomment-1757093891
I'm sorry that I have no enough time to do this recently, I'll close this
pr, sorry to waste your time to review it, also thanks for you to give
explanation to me.
--
This i
ppkarwasz commented on PR #1856:
URL: https://github.com/apache/logging-log4j2/pull/1856#issuecomment-1756963010
Closes #1829 .
--
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 commen
ppkarwasz commented on PR #1856:
URL: https://github.com/apache/logging-log4j2/pull/1856#issuecomment-1756951260
@Dreeam-qwq,
All 2.x releases must run on JDK 8. Since Disruptor 4.x requires a Java 11
runtime, we can not drop support for Disruptor 3.x.
Looking at your patch, th
Dreeam-qwq opened a new pull request, #1856:
URL: https://github.com/apache/logging-log4j2/pull/1856
Add support for disruptor 4.0.0 to close #1829 and
[LOG4J2-3595](https://issues.apache.org/jira/browse/LOG4J2-3595). Tested and
looks good.
--
This is an automated message from the A
