When a project, one, declares a dependency as optional, another project that depends upon project one will pick up the optional dependency transitively. My exception is that an optional dependency will behave as it does in Maven and will not be picked up transitively. You can run ./gradlew verifyRuntimeClasspath against the attached project to reproduce the unexpected behaviour.
When a project, one, declares a dependency as optional, another project that depends upon project one will pick up the optional dependency transitively. My exception is that an optional dependency will behave as it does in Maven and will not be picked up transitively. You can run
./gradlew verifyRuntimeClasspathagainst the attached project to reproduce the unexpected behaviour.