Daz DeBoer

While this change should work, it has some unwanted consequences due to the fact that our variant model for JVM components isn't fully fleshed out: - With the `java` plugin...

After a little bit more experimentation, here's what I think is required: 1) A new outgoing variant `Usage.RUNTIME_CLASSES_AND_RESOURCES` on `runtimeElements` that has both the classes and resources directories as artifacts....

@oehme Given my previous comments, do you still want to target this for 5.0?

But changing tests to have a local `jar` input instead of `classes` and `resources` would be a breaking change, and should probably be changed over a deprecation cycle: WDYT?

To be a bit pedantic, there's not actually any _dependency substitution_ going on here. The problem is that both 'foo' projects produce modules with exactly the same module identifier -`org.test:foo:unspecified`....

@octylFractal Thanks for the feedback. Unfortunately this PR is hitting some [hard-to-understand test failures](https://ge.gradle.org/s/tpud6st67opl4/tests/overview?outcome=failed) that will require further investigation before this change could be merged. I'm not sure if/when I'll...

We should not remove the setting altogether. The entire reason for this PR is that users are setting `org.gradle.jvmargs` _without_ specifying `MaxMetaspaceSize`, and the daemon process is consuming more and...

@eskatos I see you assigned this back to me, but I'm not sure what action can/should be taken. The current behaviour is that if you don't set _any_ jvm args,...

Instead of using `actions/cache`, I recommend that you use https://github.com/marketplace/actions/gradle-build-action which provides the same functionality with a number of other benefits. https://github.com/gradle/gradle-build-action#why-use-the-gradle-build-action

@dhadka Since it doesn't appear that this issue will be resolved any time soon, I suggest that you update the example in the README. The current example is misleading since...