Thanks a lot!!!! I know that it is internal API, but there was (is) not an official public way how to do it. We have internal system which collecting dependencies from all apps built on TeamCity to make overview which version and flavor of our app use which version of the library, it helps a lot if we have same problem.
So I don't need i in the configuration time. I just need to have own task which will have this information. I also need it just for variant which will be built actually. I will check Configuration.getIncoming().getArtifactView(), but when is good task to access it on which task I should depend? Dne pondělí 10. července 2017 17:49:10 UTC+2 Xavier Ducrohet napsal(a): > > This is all internal APIs, and won't work in 3.0 where we changed the > resolution to be lazy. You were accessing our internal model of the > resolved dependencies. > > variant.getCompileConfiguration returns the Configuration object. You'll > have to resolve/query it for the dependencies. Just don't do it during > configuration or your users won't be happy. > > Look at Configuration.getIncoming().getArtifactView() to get a list of > ResolvedArtifactResult. > > > > On Thursday, July 6, 2017 at 3:07:23 PM UTC-7, Tomáš Procházka wrote: >> >> Hi. >> >> Does anybody known how to get list of dependencies per build variant in >> the new gradle plugin 3.0.0? >> >> In 2.3.3 works this >> >> >> >> variant.getVariantData().variantDependency.packageDependencies.allAndroidDependencies >> >> .allJavaDependencies >> >> But it doesn't exist in the new plugin version. >> >> I found just variant.compileConfiguration.dependencies.dump(); but it is >> empty and instead of MavenCoordinates return some weird Dependency class >> where classifier is missing. >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
