Shan
04/18/2019, 2:01 PMh0tk3y
04/18/2019, 3:59 PMenableFeaturePreview("GRADLE_METADATA")
in settings.gradle
), kind of legacy mode. Its absence should not affect reference resolution anyway, so there must be a different cause. Could you please provide more context or share the project if it's open-source?Shan
04/18/2019, 6:57 PMorg.tenkiv.coral
on maven central <https://search.maven.org/artifact/org.tenkiv.coral/coral-jvm/2.3.2.3/jar>
). I've implemented the dependency within a different project of mine and it appears to be found correctly by gradle, but I can't import it as it says coral
is not found.common
code, even without using the enableFeaturePreview("GRADLE_METADATA")
jvm().compilations["main"].defaultSourceSet {
dependencies {
dependsOn(commonMain)
implementation(kotlin("stdlib-jdk8"))
}
}
is this how I should be doing my reliance on commonMain within my jvm target? I will try enabling the gradle_metadata feature and see if that changes anything (for now)h0tk3y
04/19/2019, 11:42 AMis this how I should be doing my reliance on commonMain within my jvm target?It's already there by default. Each target has it's main compilation's default source set depend on
commonMain
, so adding that dependsOn(commonMain)
line is not needed.Shan
04/19/2019, 3:10 PMcreate<MavenPublication>
and trying to get the jar with from(components["java"])
because I didn't realise MPPs generate a publication for you for each target. After adjusting it to publications.withType<MavenPublication>().apply
and configuring my publications the same way, my Jar is now full. I'm just assuming that creating a publication and using from(components["java"])
wasn't able to find the Jar correctly, or something to that effect, which was what was resulting in my empty jar.