Slackbot
02/08/2022, 5:51 PMmelix
02/08/2022, 5:52 PMmelix
02/08/2022, 5:52 PMVampire
02/08/2022, 6:00 PMmelix
02/08/2022, 6:04 PMVampire
02/08/2022, 6:06 PMReferencing dependency resolution results is also disallowed (e.g.,ArtifactResolutionQuery,ResolvedArtifactetc…). For example, if you reference someArtifactResultinstances, you should instead declare aResolvedComponentResultas an input to your task. Such a provider can be obtained by invokingProvider<ResolvedComponentResult>. In the same vein, if you reference someResolutionResult.getRootComponent()instances, you should instead useResolvedArtifactResultthat returns aArtifactCollection.getResolvedArtifacts()that can be mapped as an input to your task. The rule of thumb is that tasks must not reference resolved results, but lazy specifications instead, in order to do the dependency resolution at execution time.Provider<Set<ResolvedArtifactResult>>
Vampire
02/08/2022, 6:08 PMmelix
02/08/2022, 6:09 PMmelix
02/08/2022, 6:12 PMgetResolvedArtifacts(). Makes it harder to upgrade.melix
02/08/2022, 6:12 PMJendrik Johannes
02/08/2022, 6:50 PMJendrik Johannes
02/08/2022, 6:52 PMVampire
02/08/2022, 7:20 PMLouis Jacomet
02/09/2022, 8:30 AM