Sterling Greene
Sterling Greene
Could you describe how the consuming projects know what to consume today? Do they look for the same named tasks in other projects?
@mcumings Does that mean you can run something like `gradle dataGatheringTask-2024-10-15 dataGatheringTask-2024-10-20` at the same time? This would mean that one set of tasks would process 2024-10-15 and another would...
Sorry, I was out for a bit. I didn't have a chance to deeply look at the plugin, but if it's working as a query against Develocity, I think my...
Another observation... Adding a constraint like: ``` constraints { add("aarsConfig", "androidx.lifecycle:lifecycle-runtime:2.8.0-alpha02") } ``` and only depending on `androidx.core:core:1.0.0` is enough to reproduce the problem too. https://scans.gradle.com/s/66mrxwoiwyvwq/console-log?page=1#L3-L4
We're not working on this for 8.x, but we should revisit in 9.x since this impacts Android projects.
I'll take a look for 9.2
We'll take a look
I think we could just expose the `CopySpec` as a nested property and remove the setter completely. We should deprecate `setApplicationDistribution`
I would recommend that you only define a single version catalog. The default is 'libs'. This is the name that's used in the global scope and where the conflict is...
We're not addressing this in 8.x