Thanks Matt! Indeed `./mvnw clean test` does the trick. On Wed, Sep 22, 2021 at 5:54 PM Matt Sicker <boa...@gmail.com> wrote:
> 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, Sep 22, 2021 at 3:29 AM Volkan Yazıcı <vol...@yazi.ci> wrote: > > > > 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] error: module not found: org.fusesource.jansi > > [ERROR] error: module not found: org.apache.commons.compress > > [ERROR] error: module not found: com.fasterxml.jackson.dataformat.yaml > > [ERROR] error: module not found: com.fasterxml.jackson.dataformat.xml > > [ERROR] error: module not found: com.fasterxml.jackson.databind > > [ERROR] error: module not found: com.fasterxml.jackson.core > > [ERROR] error: module not found: com.conversantmedia.disruptor > > [ERROR] error: module not found: org.osgi.framework > > [ERROR] error: module not found: org.jctools.core > > [ERROR] error: module not found: com.lmax.disruptor > > [ERROR] error: module not found: org.apache.logging.log4j.plugins > > [ERROR] error: module not found: org.apache.logging.log4j > > > > Any ideas? >
