This might be related with #26.
When I modularize a simple application with a test that loads a test resource file by adding a module-info.java file in src/main/java and apply to moduleplugin to build.gradle, the test fails.
Here's a simple project that exhibits the issue: https://github.com/weiqigao/moduleplugin-test-resources-issue/tree/master/src
Runnin "gradle test --debug" reveals that module path includes
./build/classes/java/main
./build/classes/java/test
./build/resources/main
./build/resources/test
with only the ./build/classes/java/test patched into the module. To have the resources visible from inside the module, the ./build/resources/main and ./build/resources/test needs to be patched into the module as well.
This might be related with #26.
When I modularize a simple application with a test that loads a test resource file by adding a module-info.java file in src/main/java and apply to moduleplugin to build.gradle, the test fails.
Here's a simple project that exhibits the issue: https://github.com/weiqigao/moduleplugin-test-resources-issue/tree/master/src
Runnin "gradle test --debug" reveals that module path includes
with only the
./build/classes/java/testpatched into the module. To have the resources visible from inside the module, the./build/resources/mainand./build/resources/testneeds to be patched into the module as well.