It's part of NamedDomainObjectContainer. It configures the named object but if it doesn't exist, it creates it first. This is handle by gradle, it's not part of our plugin. If you have question regarding how this works internally, you post on the gradle specific forums.
On Mon, Oct 12, 2015 at 3:05 AM, wang lei <[email protected]> wrote: > Code sample: > android { > signingConfigs { > releaseStoreConfig { > storeFile file('test.keystore') > storePassword 'testpasswd' > keyAlias 'testalias' > keyPassword 'testpasswd' > } > } > } > I know the "android {closure}" is according to gradle rules: The > extensions added to the project by the plugins. Each extension is available > as a method which takes a closure or Action as a parameter. > > Also by using groovy closure implicit coercion the "signingConfig > {closure}" invokes android extension's: void signingConfigs(Action<? super > NamedDomainObjectContainer<SigningConfig>> action) > > Here is the problem: in signingConfigs closure,why 'releaseStoreConfig > {closure}' create the object and configure it, I can't find the > corresponding method. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
