has anyone had issues with this: `apply(plugin = "com.android.library")` in build scripts written in...

# multiplatform

[Kris Wong]

has anyone had issues with this: apply(plugin = "com.android.library") in build scripts written in Kotlin DSL?

[Kris Wong]

it doesn't recognize android

[alex009]

https://github.com/icerockdev/moko-template here project with kotlin-dsl, multiplatform, android, ios, multi-module...maybe this help you

[Kris Wong]

it's a nice template. was hoping to avoid this whole buildSrc concept

[alex009]

what in buildSrc should be avoided on your opinion?

[Kris Wong]

I don't want to spend the effort to migrate to that right now

[alex009]

buildsrc in template contains only dependencies definition with versions

[Kris Wong]

I can't get my plugins to apply correctly, and the few examples I am seeing seem to use the buildSrc mechanism

[louiscad]

You need to use the plugins DSL:

plugins {
    id("com.android.library") // that
    kotlin("multiplatform") // after all, you posted in MPP channel
    `maven-publish` // If you want
}

[Kris Wong]

that isn't enough as is. it doesn't know what com.android.library is

[louiscad]

@Kris Wong It's not published on gradle plugins portal so you need to add a classpath dependency in the `buildscript`'s root project, as usual in Android projects.

[Kris Wong]

still not enough. I had to add a condition in the pluginManagement block in the settings.gradle.kts

[Kris Wong]

but the IDE was still showing errors on the whole android block even in that case, which broke code navigation

[Kris Wong]

and I ain't got time for that right now 😛

[louiscad]

In #splitties, it works perfectly. All modules support android (or jvm for a few of them), and the preferences module (on develop branch) supports macOS and iOS too.

[Kris Wong]

dunno, it doesn't work in my project

[Kris Wong]

buildscript {
    extra["iosFrameworkName"] = "FeatureModule"

    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath("com.android.tools.build:gradle:3.5.1")
        classpath("org.jfrog.buildinfo:build-info-extractor-gradle:4.9.10")
    }
}

plugins {
    kotlin("multiplatform")
    id("com.android.library")
    id("maven-publish")
}

[Kris Wong]

* What went wrong:
Plugin [id: 'com.android.library'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (plugin dependency must include a version number for this source)

[Kris Wong]

I have the same issue with other plugins as well

[louiscad]

Try adding allprojects { repositories { google() } } in root project's build file

[Kris Wong]

there's only one build file. it has google() in both repositories blocks.

[alex009]

with plugins block you must use pluginsManagement block in settings.gradle.kts for resolving of artifacts.
https://github.com/icerockdev/moko-template/blob/09a117bff898add8a2338b09ed9bcfe736f38a37/settings.gradle.kts#L20
like here.

and you can move this map to settings:
https://github.com/icerockdev/moko-template/blob/09a117bff898add8a2338b09ed9bcfe736f38a37/buildSrc/src/main/kotlin/Deps.kt#L107

[alex009]

in moko-template android.library plugin already in classpath because included as dependency in buildSrc. but here sample without it:
https://github.com/icerockdev/moko-core/blob/cc196f1abc12aaea2fd81ffcb5ff289aa6378926/buildSrc/src/main/kotlin/Deps.kt#L32

[Kris Wong]

yeah it's not awesome to have to map out every plugin in another build script file when Groovy apply plugin works like a charm

[Kris Wong]

but thanks for all the info