I’m trying to write a plugin for Android, but my Gradle knowledge isn’t quite good enough yet. Specifically, I’d like to allow dynamic “blocks” (closures?) nested under some plugin extension. Case of point, in Android you can define dynamic “product flavors” like this: android { productFlavors{…

The ‘productFlavors’ block here is actually an instance of NamedDomainObjectContainer . You can create one of these by calling Project.container() and passing a container type. The type is generally a POJO, with the requirement that it must define a property called “name” and that it must have a cons…

Thanks for answering Mark, but how would Foo look like, with one more level: moo{ foos { myFoo { bar = 'some value' } } } Updated: I followed what was outlined in this small snippet: https://books.google.dk/books?id=jbgVAAAAQBAJ&pg=PA28&lpg=PA28&dq=dsl+NamedDomainObject…

You would define an extension type with a container as a property. You can take a look at an example of what that might look like here: [image] Extension containing a NamedDomainObjectContainer Help/Discuss I am working on a plugin that defines an Extension where I would …

Yeah it’s something like that I ended up doing… now I just have to figure out how to use the DSL to define dynamic build tasks inside the apply(…) method: class DistributionExtension{ final NamedDomainObjectContainer<ProductFlavor> productFlavors DistributionExtension(productFlavors){ …

“each” iterates on the collection “right now”, so when inside the “apply” method of your plug-in, the collection is empty. You want to use “productFlavors.all{}” in your case

Ahh, that difference had eluded me! Thanks for the assistance guys.

Final little twist… what if I need to add two extension types, to parse something like this (two distinct collections under the root): distributions { productFlavors{ A { uploadUUID = 'bff3750c-efeb-430b-b523-0781a6b700a3' } B { uploadUUID = '4577…

Your constructor should take multiple arguments. Also, when calling extensions.create() the last argument is actually a multiple argument list of constructor args. DistributionsExtension(productFlavors, buildTypes){ this.productFlavors = productFlavors this.buildTypes = buildTypes } extens…

Ahh… had not noticed it was a vararg type. Thanks again, I’m learning so much about Gradle I’ll have to write a blog entry about it soon.

What about checking for dynamic properties when navigating such a DSL? I thought I could just write if(distriutions.productFlavors[‘debug’] == null){ … } …but this fails: ProductFlavor with name ‘debug’ not found. I also tried with .hasProperty(‘debug’) but this is always false. I get the feeling…

How is the Android "productFlavors" mechanism implemented?

Help/Discuss

mark_vieira (Mark Vieira) September 18, 2015, 9:34pm 4

You would define an extension type with a container as a property. You can take a look at an example of what that might look like here:

Topic		Replies	Views
Make a Gradle plugin compatible with Kotlin DSL Help/Discuss android , plugins	2	2658	August 10, 2017
Task development: How to combine extensions and conventions for a richer DSL? Old Forum Archive	15	6858	March 26, 2012
Multi-level Plugin DSL with Multiple Collection Properties Help/Discuss	8	200	July 30, 2024
How can I extend the DSL dynamically? Help/Discuss	2	1661	November 14, 2016
Defining Consumer from Groovy build.gradle Help/Discuss	12	952	July 28, 2020

How is the Android "productFlavors" mechanism implemented?

Related topics