Closed ghale closed 5 years ago
Looks like the deprecations fall into three usages that are all the same sort of thing:
One more (same sort of thing):
checkBinaryCompatibility
is fixed in this PR: https://github.com/gradle/gradle/pull/7407
@lacasseio I merged PR 7407 above into master, but we probably want to put these all on release first so we don't have any surprises with a 5.0 nightly
generateGradleApiPackageList
is fixed in this PR: https://github.com/gradle/gradle/pull/7433
I will cherry-pick the commit inside release.
@lacasseio I cherry-picked it already, should have told you when we were chatting
javadocAll
is fixed in this PR: https://github.com/gradle/gradle/pull/7450
apiMetadata
is fixed in this PR: https://github.com/gradle/gradle/pull/7451
I was about to close this, but I found two more instances:
I fixed the above two cases
With the single project lock work, we have surfaced some instances in the gradle build where we are doing cross-project configuration resolution and are throwing deprecation warnings. We should investigate where we're doing this and fix them.