+1
Sigs good, build and test good, site looks fine.
—
Matt Sicker
> On Jun 28, 2022, at 19:00, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.18.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, releas
The site will get updated properly when the ongoing Log4j2 vote completes.
—
Matt Sicker
> On Jun 25, 2022, at 21:02, Robert Middleton wrote:
>
> +1
>
> Notes:
> * Copyright needs updating
> * I did not check maven artifacts, only distribution archives.
> * I did not test any code, I validated
+1
This vote closes with 3 +1 votes from myself, Remko, and Robert. I’ll continue
with the release.
—
Matt Sicker
> On Jun 25, 2022, at 21:02, Robert Middleton wrote:
>
> +1
>
> Notes:
> * Copyright needs updating
> * I did not check maven artifacts, only distribution archives.
> * I did not
If that test isn’t using the listener mechanism in LoggerContext, then it’ll
sporadically fail to detect reconfigurations.
—
Matt Sicker
> On Jun 29, 2022, at 12:13, Ralph Goers wrote:
>
> I believe I have seen this or a similar error in the past but I haven’t seen
> it myself in quite a whi
I believe I have seen this or a similar error in the past but I haven’t seen it
myself in quite a while.
I’d bet it is a problem with the test.
Ralph
> On Jun 29, 2022, at 6:50 AM, Gary Gregory wrote:
>
> I get a test failure:
>
> ERROR] Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Tim
I get a test failure:
ERROR] Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time
elapsed: 121.852 s <<< FAILURE! - in
org.apache.logging.log4j.core.config.TestConfigurator
[ERROR]
org.apache.logging.log4j.core.config.TestConfigurator.testReconfiguration
Time elapsed: 15.035 s <<< FAILURE!
j
