Sterling Greene
Sterling Greene
No longer possible to specify a executable which is not part of a Java toolchain for a JavaExec task
Instead of using `JavaExec`, could you use `Exec` instead?
I think the current behavior is right, but we need to explain this better and in a more simple way. `someProperty.set(someProvider)` is expressing an opinion that `someProvider` is the source...
If you know the name of the task, you can just do: ``` project.tasks.register("dependent") { dependsOn("testReleaseUnitTest") } ```
Nope, the names are resolved while building the task graph. ``` tasks.register("foo") { dependsOn("bar") } tasks.register("bar") ```
@tresat can we close this since you're doing something else?
Is following the instructions here https://github.com/androidx/androidx/blob/androidx-main/docs/onboarding.md the best way to checkout the appropriate version of Androidx? Just cloning https://github.com/androidx/androidx.git isn't enough to get a frameworks/support directory.
We think this has been fixed in 8.7. #28145 is going to check a few related scenarios.
@unshare I don't think we want to change this in this way. `MutableVersionConstraint` isn't intended to be implemented directly. Why do you need your own implementation? You can configure an...
@vmadalin suggested closing this until we see this happen again
This would need to change in https://github.com/gradle/gradle/blob/1aa913547db41cb664313afc89cb681e4bb1a3f7/platforms/software/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/ivyresolve/parser/PomReader.java#L66