Re: Maven test fails due to "module not found"

Based on how we had to structure the multiple compile passes to generate the proper module info, you need to run `clean` before `test`. Even if you don't call clean, in log4j-core, it has to invoke clean to remove some incorrectly-generated module info to replace it with the correct one. On Wed, S

Maven test fails due to "module not found"

Running `./mvnw test` (after a successful `./mvnw clean install -DskipTests=true` run) on `master` fails as follows: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project log4j-core: Compilation failure: Compilation failure: [ERROR

Re: Cek's new log4j vs logback benchmark

That's great news! Then I will be looking forward to your signal for putting a ribbon onto 2.15.0. I have followed the conversation with Claes Redestad from Oracle on Twitter . My conclusion was also that there apparently is no way to ma

Re: [VOTE] Release log4cxx 0.12.1

Guten Tag Robert Middleton, am Mittwoch, 22. September 2021 um 02:37 schrieben Sie: > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... +1 Successfully tested on VS Community 2019 16.11.3 on fully updated Win