Issue when used with java-modules-dependency plugin and test fixtures

[ttaxon]

When this plugin is used with the java-module-dependency plugin and testFiture is used, The following error occurs:

* What went wrong:
Could not determine the dependencies of task ':lib:test'.
> Could not resolve all dependencies for configuration ':lib:testRuntimeClasspath'.
   > Unknown Module: org.my.lib.test.fixtures

I was able to reproduce it in this repository in the samples/use-with-test-fixtures project.

The build-logic/build.gradle.kts was modified to include the dependency on the java-module-dependencies plugin:

plugins {

    `kotlin-dsl`

}


dependencies {

    implementation("org.gradlex:java-module-testing:1.5")

    implementation("org.gradlex:java-module-dependencies:1.5")

}

and the plugins configuration in build-logic/src/main/kotlin/org.my.gradle.java-module.gradle.kts was modified to include the java-modules-dependencies plugin:

plugins {

    id("java")

    id("java-test-fixtures")

    id("org.my.gradle.base")

    id("org.gradlex.java-module-testing")

    id("org.gradlex.java-module-dependencies")

}

With those two modifications in place, when the command:

../../gradlew :lib:test

is run, the following output is generated:

$ ../../gradlew :lib:test
Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :java-module-testing
Signing plugin detected. Will automatically sign the published artifacts.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':lib:test'.
> Could not resolve all dependencies for configuration ':lib:testRuntimeClasspath'.
   > Unknown Module: org.my.lib.test.fixtures

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 35s
13 actionable tasks: 5 executed, 8 up-to-date

[jjohannes]

Thank you for reporting @ttaxon. This is a bug in the integration between the two plugins.

When using requires.add("org.my.lib.test.fixtures"), the mechanism that maps Module Names to GA Coordinates of the java-module-dependencies plugin is used (if the plugin is applied). But it is not used fully in this case. I have to investigate.

A workaround is to trick the mechanism in not attempting to find the test fixtures module. In practice, the plugin does not need to do anything here, because Gradle already sets up the dependency between the "test" and "testFixtures" source sets.

In the sample, you can add the following to lib/build.gradle.kts

// Workaround for https://github.com/gradlex-org/java-module-testing/issues/85
javaModuleDependencies.moduleNameToGA.put("org.my.lib.test.fixtures", "${project.group}:${project.name}")

[jjohannes]

Fixed in 1.6. Please let me know if you encounter any other issues @ttaxon.