If I have a multiplatform child project with 2 JVM targets, how can I select one target as a depende...

# multiplatform

[Dico]

If I have a multiplatform child project with 2 JVM targets, how can I select one target as a dependency in gradle?

[Dominaezzz]

implementation "com.dico:library-jvmFirst:1.0.0" instead of just implementation "com.dico:library-jvm:1.0.0" or implementation "com.dico:library:1.0.0".

[Dominaezzz]

I'm not sure if I've understood your question actually. Could you expand?

[Dico]

So I have a multiplatform project

[Dico]

A child project should be used as a dependency

[Dico]

It has 2 JVM targets

[Dico]

Before I had 1, I can do api(project(":child"))

[Dico]

It will find the jvm target and add it as a dependency.

[Dico]

I tried getting the source set from the child project and using dependsOn in my root source set, but it seems to assume that the source set will be from the same project

[Dominaezzz]

Ah, you need to select the specific artifact but I can't find docs about it.

[Dico]

sourceSets["jvmMain"].apply {
    val targetName = (findProperty("platform")?.toString() ?: "remote") + "Jvm"
    val target = platform.kotlin.targets[targetName]
    val jarTask = platform.tasks.getByName(target.artifactsTaskName) as Jar
    val platform = jarTask.archiveFile.get().asFile

    dependencies {
        api(engine)
        api(platform)
    }
}

[Dico]

Here:

dependencies {
    api(project(":platform", "myTargetJvmApiElements")
}

[Dominaezzz]

Did that work?

[Dico]

Both of them work.

[Dico]

And with both of them, IntelliJ doesn't recognize the dependencies, so everything is red.

[Dico]

But the compile task works fine.

[louiscad]

Did you report it on kotl.in/issue?

[Dico]

Actually, the compileKotlinMetadata doesn't work.

[Dico]

compileKotlinJvm is fine

[Dico]

There's no "commonMainApiElements"

[Dico]

Does an api configuration extend an implementation configuration? @louiscad I think you might know this

[Dico]

Or is it the other way around? wait...

[louiscad]

api is implementation + api

[Dico]

val platform = project(":platform")
val configurationName = (findProperty("platform")?.toString() ?: "remote") + "JvmApiElements"

sourceSets["commonMain"].dependencies {
    api(engine)
    api(platform)
}

sourceSets["jvmMain"].dependencies {
    api(engine)
    api(project(":platform", configurationName))
}

[Dico]

works!

[louiscad]

@Dico Isn't api(engine) a duplicate in jvmMain?

[Dico]

Is it? I always do it like this

[louiscad]

I do it only for per platform artifacts

[Dico]

Ah it figures that part out if I put it in common. Awesome!

[louiscad]

If you're using gradle metadata, yes

[louiscad]

If the library is also compatible with gradle metadata

[Dico]

I am, I thought it just figures out which target to use from the project

[Dico]

but it does the same then for the other target sif its in common