Sterling Greene
Sterling Greene
We'll take a look at this and see if it can be merged for 8.14 or if it needs to wait for 9.0. Worst case is that this will wait...
We think this may be resolved after we migrate to Provider API and remove internal convention mapping. I've added it to 9.0 to confirm when we get there.
We primarily recommend using the plugin approach internally: https://github.com/gradle/gradle/blob/master/architecture/standards/0006-use-of-provider-apis-in-gradle.md But we sometimes have to use other approaches due to backwards compatibility.
https://github.com/gradle/gradle/pull/32233/files
Alternatively, `--write-locks` could change the behavior of `dependencies` to fail the build or hide output. Or we should have a task similar to `dependencies` that is specifically made for writing...
I don't think we intentionally want the current behavior. I think the fix for this is to not use `withExtension` at all. It looks like we're getting a partial path...
There's a real issue with plugin ordering and how convention mapping (an internal feature that predates Property conventions) are applied. `classpath += files(...)` eagerly resolves the current value of `classpath`...
Let's see what this looks like in the latest version and if we've already changed this output.
@jfresen I know it's been awhile, but do you have a reproducer or what the dependencies were that produced this error?
Hi @urdak, Thanks for the PR. Right now, we're not sure that we want to expand `ProjectBuilder` and add new APIs to it. There are a few issues (not with...