-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with Kotlin Multiplatform plugin #129
Comments
I found a way to configure the task that produces the JAR file used for the graalVM native image or shared lib. There are some things that make it complicated:
Additionally I would remove the hard dependecy to the Java plugin, so there are only thise tasks that the user wants to be configured. |
@JotBePunkt Is it possible to share your working build.gradle(.kts) ? I'm struggling with the same pain points. |
I did not make it work yet, as described I would need to refactor the plugin. I did not get a reaction from one of the contributors, I dont know if this is welcome or not. |
Just hit this
File is ./build/libs/emulator-tools-jvm-kmp-f632f62-dirty.jar |
Seems like a bug in the Jar task - |
I think the assumption of
|
Working around with
|
Advice on gradle/gradle#19449 seems to be assume a default of the jar plugin, but always allow overriding this in the plugin config. |
With a kts build file.
|
Looks like the classpath needs to be jvmRuntimeClasspath not runtimeClasspath here
|
Hi,
i wanted to use the plugin to build an image of a project I built with the Kotlin Multiplatform project (in fact I wanted to compare GraalVM and Kotlin Native). The Kotlin Plugin does not create a
<projectName>-<version>.jar
but a<projectName>-<version>-jvm.jar
For this case it would be create to configure the Jar file to be use (or its classifier (in this case
jvm
))The text was updated successfully, but these errors were encountered: