How do you use convention plugins to setup the sdk...

# android

[hfhbd]

How do you use convention plugins to setup the sdk of a android application and android library? Ideally, I want to apply a base android plugin to get the android extension with the type of CommonExtension

[Daniel B Duval]

You’ll want to take this to here - https://gradle-community.slack.com/archives/CJYS1DAP5

[galex]

Look at nowinandroid in Github

[hfhbd]

Thanks for the link, but they also configure the library and the application separately: https://github.com/android/nowinandroid/blob/e82a3d9621c7fb0993b7ac56b5a5ae2a92893a39/build-logic/convention/src/main/kotlin/AndroidLibraryConventionPlugin.kt#L39 and https://github.com/android/nowinandroid/blob/e82a3d9621c7fb0993b7ac56b5a5ae2a92893a39/build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt#L34
But yeah, with "normal" (no script) plugins you could extract this config to a common place to reuse it

[Daniel B Duval]

The Gradle slack workspace I linked above would be a great place for this question. There’s an Android channel in there that gets contributions from both Gradle and AGP contributors.
To do this, it’s rather simple.
In your build-conventions source, you’d have your script, e.g., myapplication-application-conventions and myapplication-library-conventions as a plug in script.
At the top of the convention, you’d apply the plug in. e.g (in library convetion):

plugins {
  id("com.android.library")
}

android {
  //build logic for all libraries
}

Then in a library build script (same would hold for your application):

plugins {
  id("myapplication-library-conventions")
}

// add anything additional the library may need, such as testNamespace

[hfhbd]

Yeah, implementing the plugins is easy. I was more surprised to see no common android plugin provinding a CommonExtension.

[Daniel B Duval]

Isn’t that what ApplicationExtension , DynamicFeatureExtension , LibraryExtension and TestExtension are?