We release the source code of the plugin after every stable release, so the 2.2 source code is not available yet.
The only way in which we expose the final, effective dependency graph is in "the model". What you can try to do is use Gradle's Tooling API to get the model, i.e. an instance of the AndroidProject class that is in the com.android.tools.build:builder-model Maven artifact. This is how the IDE gets all the dependency information. Other than that you can file a bug at b.android.com to request this information to be more easily accessible from within build.gradle. HTH, Michal On Thu, Aug 18, 2016 at 5:13 PM Tomáš Procházka <tomas.procha...@gmail.com> wrote: > My colleague tried to reply to this thread but it looks that his reply was > not allowed by forum admin or something like this. > By we have tasks which collect list of all dependencies of all variants a > publish it to the our server for analysis. > So we need the way how to get list of all resolved dependencies included > all transitive dependencies. > > > Dne úterý 19. července 2016 12:07:47 UTC+2 Michal Bendowski napsal(a): > > Hi! > > Sorry for a late reply. We missed the ZipAlign problem, thanks for > reporting, we'll investigate. VariantDependencies is not a public API so we > reserve the right to break it, sorry. What exactly is your use case for > using it? > > Michal > > On Monday, July 11, 2016 at 5:14:39 PM UTC+1, Tomáš Procházka wrote: > > It looks that between 2.1.2 and 2.2.0-alpha they are many API changes. > For example we are using custom remote APK signing with this code wich > doesn't work now because ZipAlign task require some manifest property now. > https://gist.github.com/tprochazka/db02753546066d97edf40572b5b57b91 > > There is some more official way how to just override sign task without > re-configuring zip aplign task? > > > Another change is that 'libraries' was removed from > com.android.build.gradle.internal.dependency.VariantDependencies > We are using it for list off all variant dependencies. > There is pubic API for this? > > And I also found that com.android.manifmerger.ManifestMerger and import > com.android.manifmerger.MergerXmlUtils is missing, maybe just moved to the > different package. > I don't check this yet. > > Thanks for reply. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "adt-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adt-dev/UzT1Ko_5YdY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adt-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
