rocketraman11/08/2023, 9:44 PM
Upon investigation, it appears that kvision now assumes the existence of a jvmRun with a mainClass property (https://github.com/rjaros/kvision/blob/master/kvision-tools/kvision-gradle-plugin/src/main/kotlin/io/kvision/gradle/KVisionPlugin.kt#L296). However, my project structure is as follows: • shared -- has kvision plugin, but no application plugin -- this is a library so there is no
* What went wrong: A problem occurred configuring project ':shared'. > Cannot query the value of task ':shared:jvmRun' property 'mainClass' because it has no value available
• backend -- has application plugin, and therefore has a
• client @Robert Jaros what do you think? Can we add a config setting on the kvision plugin to not provide any jar functionality? I take care of this on my own.