Gary Hale
Gary Hale
I think it involves parsing the logs, but that it should also be pretty simple. See how we do this in the Gradle tests: https://github.com/gradle/gradle/blob/be4603f6a1ecb209b26508d068927cb01cb730d4/subprojects/internal-integ-testing/src/main/groovy/org/gradle/integtests/fixtures/executer/AbstractGradleExecuter.java#L1352-L1360. We don't have to do...
@h0tk3y My understanding from parsing through the conversation above and playing around with the reproducer is the following: - The issue caused by the change in behavior between Gradle 7.3...
So, the `ToolChain` object is not intended to be a query API. Instead, it's intended as a specification API for setting up a custom toolchain. Which is to say, the...
@bot-gradle test this
@bot-gradle test this
I'm closing this for now in favor of a different approach where we just capture "rules" that are applied to software type objects when they're referenced in a project.
It probably makes sense to just leave this task always out-of-date for now. The input for this task is the `Module` object, which isn't a Gradle-specific object, so adding nested...
Previously, the deploy task was doing this work itself by reaching across project boundaries (unsafely) and gathering this information from each project directly. It was also doing this sequentially, rather...
@bot-gradle test this
@bot-gradle test this