将SLF与Java9模块一起使用

Question

I set up a small test project using java 9 modules. The structure looks like this:

.
├── build.gradle
└── src
    ├── main
    │   └── java
    │       ├── module-info.java
    │       └── slfTest
    │           └── Main.java
    └── test
        └── java
            └── slfTest
                └── MainTest.java

(Feel free to clone and have a look yourself: git clone https://github.com/michas2/slfTest.git )

The classes Main and Main Test only log some simple output:

    Logger logger = LoggerFactory.getLogger(Main.class);
    logger.info("Hello World");

Now gradle run works as expected, but gradle test gives a ClassCastException.

    $ gradle run -q
    [main] INFO slfTest.Main - Hello World
    $ gradle test -q
    java.lang.ClassCastException: org.slf4j.simple/org.slf4j.simple.SimpleLoggerFactory cannot be cast to org.gradle.internal.logging.slf4j.OutputEventListenerBackedLoggerContext
            at org.gradle.internal.logging.slf4j.Slf4jLoggingConfigurer.configure(Slf4jLoggingConfigurer.java:42)
            at org.gradle.internal.logging.config.LoggingSystemAdapter.startCapture(LoggingSystemAdapter.java:54)
            at org.gradle.internal.logging.services.DefaultLoggingManager$StartableLoggingSystem.start(DefaultLoggingManager.java:297)
            at org.gradle.internal.logging.services.DefaultLoggingManager.start(DefaultLoggingManager.java:73)
            at org.gradle.internal.logging.services.DefaultLoggingManager.start(DefaultLoggingManager.java:37)
            at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:83)
            at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:64)
            at worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:62)
            at worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:67)

Removing the java 9 module makes things work again. Therefore I assume there is module access problem. - What is the right way to fix it?

---

The content of module-info.java is:

module slfTest {
    requires  org.slf4j;
    exports slfTest;
}

When gradle runs the tests, gradle tries to inject its own logging backend. - Guess this is the part where some module access problem arise.

Answer 1

This is a known issue in gradle.

For more reference see here at

1. Depending on slf4j causes test worker throw ClassCastException
2. SLF4J ClassCastException when testing with custom system ClassLoader or Java 9+